Wireless data communication interface

ABSTRACT

In some embodiments, the rendering a financial transaction record in a second format includes converting a tokenized first item of financial transaction information to an account-specific item of financial transaction information using an account identifier associated with the tokenized first item in a registry stored in a secured account data vault. In some embodiments, the system includes a transaction execution module for transmitting in the second format the first item of financial transaction information for payment processing by the first external financial party, wherein the second format includes the financial transaction information using the account identifier associated with the tokenized first item in a registry stored in a secured account data vault, and transmitting in the third format the second item of financial transaction information for payment processing by the second external financial party.

CLAIMS TO PRIORITY

This application further claims benefit of priority of U.S. ProvisionalApplication Serial No. 62/028,763 entitled “Methods and Apparatus forUnified Inventory and Financial Transaction Management” filed Jul. 25,2014, the content of which is incorporated by reference herein in itsentirety and for all purposes.

This application further claims benefit of priority of U.S. ProvisionalApplication Serial No. 62/028,993 entitled “Methods and Apparatus forUnified Inventory and Financial Transaction Management” filed Jul. 25,2014, the content of which is incorporated by reference herein in itsentirety and for all purposes.

This application further claims benefit of priority of U.S. ProvisionalApplication Serial No. 62/030,335 entitled “Methods and Apparatus forUnified Inventory Management” filed Jul. 25, 2014, the content of whichis incorporated by reference herein in its entirety and for allpurposes.

This application further claims benefit of priority of U.S. ProvisionalApplication Serial No. 62/081,329 entitled “Wireless Data CommunicationInterface” filed Nov. 18, 2014, the content of which is incorporated byreference herein in its entirety and for all purposes.

BACKGROUND Description of the Related Art

Mobile commerce, colloquially known as wireless commerce or wirelesspayment, includes the buying and selling of products or services withpayment facilitated over mobile or wireless electronic payment systemssuch as the Internet-connected cellular phones, tablets, and otherwirelessly computer network-connected hardware. The amount of tradeconducted electronically has grown rapidly with widespread Internetusage and has further increased with the proliferation of mobilecomputing devices capable of accessing the Internet. Such mobilecomputing devices include laptop computers, tablet computers, andhandheld telephones.

Most wireless commerce still frequently involves fulfillment of an orderthrough the acquisition of physical items by a purchaser who pays at thepoint of sale through a tangible payment credential backed by issuingfinancial institution. In the majority of transactions, the purchasetransaction is slowed by the necessity of presenting a physicalcredential that is then manually converted to a representation aselectronic signals (e.g., by scanning a credit card) at the point ofsale for remote verification prior to transaction completion through thedelivery of a physical package containing goods.

In today's environment, however, merchants encounter a bottleneck totransaction completion as the physical credential is converted to arepresentation as electronic signals (e.g., by scanning a credit card)at the point of sale, creating significant technology roadblocks in thejourney to omnichannel commerce. These roadblocks, or friction points,can hamper a merchant's ability to deploy new sales channels; reach newand existing customers with relevant, effective promotions and offers;and ultimately expand their businesses. In other words, these frictionpoints can prevent a business from operating smoothly and reaching itsfull potential.

These friction points include communication support to enable a paymentservice provider to process payments across multiple channels, some ofwhich involve wireless transaction communication. Today, many merchantsmust rely on separate payments providers for their in-store, e-commerce,and mobile (wireless) sales, with significant manual interventions.

These friction points, especially with regard to inadequacies inwireless communication infrastructure in mobile (wireless) throttle thecommunication of information useful to sales in many channels ofcommerce.

SUMMARY

Some embodiments include a system for providing a wireless datacommunication interface. In some embodiments, the system includes one ormore computers configured to implement by executing instructions on oneor more processors a platform-agnostic wireless data communicationsystem. In some embodiments, the system includes one or more receivingmodules for receiving over a wireless data communication channel atokenized first item of financial transaction information from acustomer mobile device presenting a customer-facing interface, andreceiving a second item of financial transaction information from amerchant-facing point-of-sale interface connected to the mobile devicethrough the wireless data communication channel. In some embodiments,the system includes a point of sale server for rendering in a commoninternal format the first item of financial transaction information fromthe customer-facing interface, and rendering in the common internalformat the second item of financial transaction information from themerchant-facing point-of-sale interface.

In some embodiments, the system includes a payment processing module forrendering in a second format the first item of financial transactioninformation for payment processing by a first external financial party.In some embodiments, the rendering in the second format comprisesconverting the tokenized first item of financial transaction informationto an account-specific item of financial transaction information usingan account identifier associated with the tokenized first item in aregistry stored in a secured account data vault. In some embodiments,the system includes a payment processing module for rendering in a thirdformat the second item of financial transaction information for paymentprocessing by a second external financial party. In some embodiments,the system includes a transaction execution module for transmitting inthe second format the first item of financial transaction informationfor payment processing by the first external financial party. In someembodiments, the second format includes the financial transactioninformation using the account identifier associated with the tokenizedfirst item in a registry stored in a secured account data vault, andtransmitting in the third format the second item of financialtransaction information for payment processing by the second externalfinancial party.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a distributed system that may implement a wireless datacommunication interface, according to some embodiments.

FIG. 2A illustrates a module that may implement a wireless datacommunication interface, according to some embodiments.

FIG. 2B is a flowchart of a process for a wireless data communicationinterface, according to some embodiments.

FIG. 2C is a flowchart of a process for a wireless data communicationinterface, according to some embodiments.

FIG. 2D is a flowchart of a process on a customer mobile device for awireless data communication interface, according to some embodiments.

FIG. 2E is a flowchart of a process on a unit of merchant-facing POShardware for a wireless data communication interface, according to someembodiments.

FIG. 2F is a flowchart of a process on a unit of merchant-facing POShardware for a wireless data communication interface, according to someembodiments.

FIG. 2G is a flowchart of a process on a unit of merchant-facing POShardware for a wireless data communication interface, according to someembodiments.

FIG. 3 depicts a module that may implement unified inventory andfinancial transaction management, according to some embodiments.

FIG. 4 illustrates a module that may implement unified inventory andfinancial transaction management, according to some embodiments.

FIG. 5 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments.

FIG. 6 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments.

FIG. 7 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments.

FIG. 8 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments.

FIG. 9 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments.

FIG. 10A illustrates a distributed system that may implement unifiedinventory and financial transaction management, according to someembodiments.

FIG. 10B is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments.

FIG. 11 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments.

FIG. 12 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments.

FIG. 13 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments.

FIG. 14 is a user interface for creating a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 15 is a user interface for creating a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 16 is a user interface for creating a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 17 is a user interface for creating a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 18 is a user interface for creating a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 19 is a user interface for selecting for review a sales ticket forunified inventory and financial transaction management, according tosome embodiments.

FIG. 20 is a user interface for reviewing a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 21 is a user interface for selecting for review an item in a salesticket for unified inventory and financial transaction management,according to some embodiments.

FIG. 22 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 23 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 24 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 25 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 26 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 27 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 28 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 29 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 30 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 31 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 32 is a user interface for reviewing an overview of inventory in asystem for unified inventory and financial transaction management,according to some embodiments.

FIG. 33 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 34 is a user interface for recording a transaction in a system forunified inventory and financial transaction management, according tosome embodiments.

FIG. 35 is a user interface for reporting a transaction in a system forunified inventory and financial transaction management, according tosome embodiments.

FIG. 36 is a flowchart of a synchronization method for unified inventoryand financial transaction management, according to some embodiments.

FIG. 37 is a flowchart of a method for unified inventory transactionmanagement, according to some embodiments.

FIG. 38 is a flowchart of a method for unified inventory transactionmanagement, according to some embodiments.

FIG. 39 is a flowchart of a method for unified inventory transactionmanagement, according to some embodiments.

FIG. 40 is a flowchart of a method for unified inventory transactionmanagement, according to some embodiments.

FIG. 41 illustrates an example computer system that may be used inembodiments.

While the invention is described herein by way of example for severalembodiments and illustrative drawings, those skilled in the art willrecognize that the invention is not limited to the embodiments ordrawings described. It should be understood, that the drawings anddetailed description thereto are not intended to limit the invention tothe particular form disclosed, but on the contrary, the intention is tocover all modifications, equivalents and alternatives falling within thespirit and scope of the present invention. The headings used herein arefor organizational purposes only and are not meant to be used to limitthe scope of the description. As used throughout this application, theword “may” is used in a permissive sense (i.e., meaning having thepotential to), rather than the mandatory sense (i.e., meaning must).Similarly, the words “include”, “including”, and “includes” meanincluding, but not limited to.

DETAILED DESCRIPTION OF EMBODIMENTS

Brief Introduction to Wireless Data Communication Interfaces forElectronic Commerce Management Facilitating Omnichannel Commerce

Some embodiments include a system for providing a wireless datacommunication interface. In some embodiments, the system includes one ormore computers configured to implement by executing instructions on oneor more processors a platform-agnostic wireless data communicationsystem. In some embodiments, the system includes one or more receivingmodules for receiving over a wireless data communication channel atokenized first item of financial transaction information from acustomer mobile device presenting a customer-facing interface, andreceiving a second item of financial transaction information from amerchant-facing point-of-sale interface connected to the mobile devicethrough the wireless data communication channel. In some embodiments,the system includes a point of sale server for rendering in a commoninternal format the first item of financial transaction information fromthe customer-facing interface, and rendering in the common internalformat the second item of financial transaction information from themerchant-facing point-of-sale interface.

In some embodiments, the system includes a payment processing module forrendering in a second format the first item of financial transactioninformation for payment processing by a first external financial party.In some embodiments, the rendering in the second format includesconverting the tokenized first item of financial transaction informationto an account-specific item of financial transaction information usingan account identifier associated with the tokenized first item in aregistry stored in a secured account data vault. In some embodiments,the system includes a payment processing module for rendering in a thirdformat the second item of financial transaction information for paymentprocessing by a second external financial party. In some embodiments,the system includes a transaction execution module for transmitting inthe second format the first item of financial transaction informationfor payment processing by the first external financial party, whereinthe second format includes the financial transaction information usingthe account identifier associated with the tokenized first item in aregistry stored in a secured account data vault, and transmitting in thethird format the second item of financial transaction information forpayment processing by the second external financial party.

In some embodiments, the system includes an authentication module forrecognizing a customer mobile device located in an area defined within ageofence, identifying a customer associated with the customer mobiledevice based at least in part on a presence of an application executingon the customer mobile device, and issuing a session token to theapplication on the customer mobile device.

In some embodiments, the transmitting in the second format the firstitem of financial transaction information for payment processing by thefirst external financial party, includes transmitting in the secondformat the first item of financial transaction information for paymentprocessing by the first external financial party such that the secondformat includes the financial transaction information using the accountidentifier associated with the tokenized first item in a registry storedin the secured account data vault without transmitting the financialtransaction information using the account identifier associated with thetokenized first item in the registry stored in the secured account datavault to the merchant-facing point-of-sale interface.

In some embodiments, the receiving over a wireless data communicationchannel a tokenized first item of financial transaction information froma customer mobile device presenting a customer-facing interface furtherincludes receiving over a Bluetooth low energy radio communicationchannel a tokenized first item of financial transaction information froma customer mobile device presenting a customer-facing interface. In someembodiments, the receiving a second item of financial transactioninformation from a merchant-facing point-of-sale interface connected tothe mobile device through the wireless data communication channelfurther includes receiving over a broadband wireless network a seconditem of financial transaction information from a merchant-facingpoint-of-sale interface connected to the mobile device through thewireless data communication channel.

In some embodiments, the one or more receiving modules include a singlestack application program interface residing on one of the one or moreservers. In some embodiments, the transaction execution module isfurther configured for receiving on the one or more servers atransaction authorization confirmation from the first external financialparty, and the point of sale server is further configured fortransmitting to the customer-facing interface an indication of thetransaction authorization confirmation. In some embodiments, the paymentprocessing module includes a payment processing gateway forcommunicating with servers of external financial processors usingencrypted links over a network.

Some embodiments include a method for providing a wireless datacommunication interface. In some embodiments, the method includes one ormore computers executing instructions on one or more processors for awireless data communication interface method. In some embodiments, themethod includes one or more receiving modules receiving over a wirelessdata communication channel a tokenized first item of financialtransaction information from a customer mobile device presenting acustomer-facing interface. In some embodiments, the method includes oneor more receiving modules receiving a second item of financialtransaction information from a merchant-facing point-of-sale interfaceconnected to the mobile device through the wireless data communicationchannel.

In some embodiments, the method includes a point of sale serverrendering in a common internal format the first item of financialtransaction information from the customer-facing interface. In someembodiments, the method includes the point of sale server rendering inthe common internal format the second item of financial transactioninformation from the merchant-facing point-of-sale interface.

In some embodiments, the method includes a payment processing modulerendering in a second format the first item of financial transactioninformation for payment processing by a first external financial party.In some embodiments, the rendering in the second format includesconverting the tokenized first item of financial transaction informationto an account-specific item of financial transaction information usingan account identifier associated with the tokenized first item in aregistry stored in a secured account data vault. In some embodiments,the method includes the payment processing module rendering in a thirdformat the second item of financial transaction information for paymentprocessing by a second external financial party.

In some embodiments, the method includes a transaction execution moduletransmitting in the second format the first item of financialtransaction information for payment processing by the first externalfinancial party, wherein the second format includes the financialtransaction information using the account identifier associated with thetokenized first item in a registry stored in a secured account datavault. In some embodiments, the method includes the payment processingmodule transmitting in the third format the second item of financialtransaction information for payment processing by the second externalfinancial party.

In some embodiments, the method includes an authentication modulerecognizing a customer mobile device located in an area defined within ageofence, identifying a customer associated with the customer mobiledevice based at least in part on a presence of an application executingon the customer mobile device, and issuing a session token to theapplication on the customer mobile device.

In some embodiments, the transmitting in the second format the firstitem of financial transaction information for payment processing by thefirst external financial party further includes transmitting in thesecond format the first item of financial transaction information forpayment processing by the first external financial party, wherein thesecond format includes the financial transaction information using theaccount identifier associated with the tokenized first item in aregistry stored in the secured account data vault without transmittingthe financial transaction information using the account identifierassociated with the tokenized first item in the registry stored in thesecured account data vault to the merchant-facing point-of-saleinterface.

In some embodiments, the receiving over a wireless data communicationchannel a tokenized first item of financial transaction information froma customer mobile device presenting a customer-facing interface furtherincludes receiving over a Bluetooth low energy radio communicationchannel a tokenized first item of financial transaction information froma customer mobile device presenting a customer-facing interface. In someembodiments, the receiving a second item of financial transactioninformation from a merchant-facing point-of-sale interface connected tothe mobile device through the wireless data communication channelfurther includes receiving over a broadband wireless network a seconditem of financial transaction information from a merchant-facingpoint-of-sale interface connected to the mobile device through thewireless data communication channel.

In some embodiments, the one or more receiving modules include a singlestack application program interface residing on one of the one or moreservers. In some embodiments, the transaction execution module isfurther configured for receiving on the one or more servers atransaction authorization confirmation from the first external financialparty, and the point of sale server is further configured fortransmitting to the customer-facing interface an indication of thetransaction authorization confirmation. In some embodiments, the paymentprocessing module includes a payment processing gateway forcommunicating with servers of external financial processors usingencrypted links over a network.

Some embodiments include a non-transitory computer-readable storagemedium storing program instructions for providing a wireless datacommunication interface. In some embodiments, the program instructionsare computer-executable to implement one or more receiving modulesreceiving over a wireless data communication channel a tokenized firstitem of financial transaction information from a customer mobile devicepresenting a customer-facing interface. In some embodiments, the programinstructions are computer-executable to implement one or more receivingmodules receiving a second item of financial transaction informationfrom a merchant-facing point-of-sale interface connected to the mobiledevice through the wireless data communication channel.

In some embodiments, the program instructions are computer-executable toimplement a point of sale server rendering in a common internal formatthe first item of financial transaction information from thecustomer-facing interface. In some embodiments, the program instructionsare computer-executable to implement the point of sale server renderingin the common internal format the second item of financial transactioninformation from the merchant-facing point-of-sale interface.

In some embodiments, the program instructions are computer-executable toimplement a payment processing module rendering in a second format thefirst item of financial transaction information for payment processingby a first external financial party. In some embodiments, the renderingin the second format includes converting the tokenized first item offinancial transaction information to an account-specific item offinancial transaction information using an account identifier associatedwith the tokenized first item in a registry stored in a secured accountdata vault. In some embodiments, the program instructions arecomputer-executable to implement the payment processing module renderingin a third format the second item of financial transaction informationfor payment processing by a second external financial party.

In some embodiments, the program instructions are computer-executable toimplement a transaction execution module transmitting in the secondformat the first item of financial transaction information for paymentprocessing by the first external financial party, wherein the secondformat includes the financial transaction information using the accountidentifier associated with the tokenized first item in a registry storedin a secured account data vault. In some embodiments, the programinstructions are computer-executable to implement the payment processingmodule transmitting in the third format the second item of financialtransaction information for payment processing by the second externalfinancial party.

In some embodiments, the program instructions are computer-executable toimplement an authentication module recognizing a customer mobile devicelocated in an area defined within a geofence, identifying a customerassociated with the customer mobile device based at least in part on apresence of an application executing on the customer mobile device, andissuing a session token to the application on the customer mobiledevice.

In some embodiments, the program instructions computer executable toimplement the transmitting in the second format the first item offinancial transaction information for payment processing by the firstexternal financial party further include program instructions computerexecutable to implement transmitting in the second format the first itemof financial transaction information for payment processing by the firstexternal financial party, wherein the second format includes thefinancial transaction information using the account identifierassociated with the tokenized first item in a registry stored in thesecured account data vault without transmitting the financialtransaction information using the account identifier associated with thetokenized first item in the registry stored in the secured account datavault to the merchant-facing point-of-sale interface.

In some embodiments, the program instructions computer executable toimplement receiving over a wireless data communication channel atokenized first item of financial transaction information from acustomer mobile device presenting a customer-facing interface furtherinclude program instructions computer executable to implement receivingover a Bluetooth low energy radio communication channel a tokenizedfirst item of financial transaction information from a customer mobiledevice presenting a customer-facing interface.

In some embodiments, the program instructions computer executable toimplement receiving a second item of financial transaction informationfrom a merchant-facing point-of-sale interface connected to the mobiledevice through the wireless data communication channel further includeprogram instructions computer executable to implement receiving over abroadband wireless network a second item of financial transactioninformation from a merchant-facing point-of-sale interface connected tothe mobile device through the wireless data communication channel.

In some embodiments, the program instructions are computer-executable toimplement the one or more receiving modules include a single stackapplication program interface residing on one of the one or moreservers.

In some embodiments, the transaction execution module is furtherconfigured for receiving on the one or more servers a transactionauthorization confirmation from the first external financial party, andthe point of sale server is further configured for transmitting to thecustomer-facing interface an indication of the transaction authorizationconfirmation.

Brief Introduction to Electronic Commerce Management for OmnichannelCommerce Enabled by Wireless Data Communication Interfaces

Some embodiments include a system for unified inventory and financialtransaction management through which a single commercial transactiontriggers an integrated system to perform series of both inventory andfinancial operations as a unified operation as described herein. Someembodiments reduce the complications and unnecessary costs of managingpayments partnerships across multiple channels that bring friction intoa merchant's business and present artificial barriers to success. Insome embodiments, a system for unified inventory and financialtransaction management reduces friction caused by disparate processingrates, extra reconciliation paperwork and misaligned inventory byproviding an all-in-one payments solution capable, in some embodiments,of receiving data from multiple customer touchpoints across multipleones of a merchant's channels.

In some embodiments, friction points can be eliminated with theimplementation of a system for unified inventory and financialtransaction management in multiple channels. Some embodiments of asystem for unified inventory and financial transaction management acceptmobile, online and point-of-sale payments under a single merchantaccount, providing room scaling that allows merchants to take advantageof new opportunities for expansion and growth.

Some embodiments of a system for unified inventory and financialtransaction management support a merchant that operates a physicalstore, operates an online store, accepts payments on a mobile device, orany combination of those channels. Some embodiments of a system forunified inventory and financial transaction management present a singlemerchant account to reduce reconciliation and accounting headaches andto provide one version of the data through consolidated reports acrossall channels and touchpoints. Some embodiments of a system for unifiedinventory and financial transaction management can also handle theissues of managing inventory across mobile and e-commerce touchpoints,as well as in the store, providing a single view of the merchandisethat's available to sell, and helping businesses balance betweeninventory and demand.

Some embodiments of a system for unified inventory and financialtransaction management support a cloud-based point-of-sale, mobile andeCommerce framework that integrates payments with inventory management.

Some embodiments of a system for unified inventory and financialtransaction management real-time, in-app inventory tracking, managementand replenishment directly from a mobile application. Some embodimentsof a system for unified inventory and financial transaction managementprovide import and export capabilities that allow merchants to easilytransfer and integrate inventory data into other systems. Someembodiments of a system for unified inventory and financial transactionmanagement provide Integration with third party eCommerceplatforms—sales and inventory data by location provides merchants morevaluable insights into their business. Some embodiments of a system forunified inventory and financial transaction management provide theability to set replenishment thresholds and alerts and transferinventory between locations and channels. Some embodiments of a systemfor unified inventory and financial transaction management adjustinventory for sales and returns in real-time and can also work with amerchant's existing inventory platform, by allowing merchants tointegrate in to some embodiments of a system for unified inventory andfinancial transaction management using application program interfaces.

Some embodiments of a system for unified inventory and financialtransaction management can also solve the problems of the frictionpoints mentioned above by eliminating disparate payment processors andprocessing rates, further simplifying reconciliation across all of amerchant's selling channels. In moving to a single payments providerunder some embodiments, merchants can also take advantage of volumepricing, and get the best possible rates for each channel.

Some embodiments of a system for unified inventory and financialtransaction management provide business insights, such merchants canleverage data to optimize sales, for example such as how much floorspace to allocate to specific products, what items and locations providethe most revenue and profit and what products to feature. Merchants alsohave the ability to store customer history, past purchases and othercustomer-specific data to help them become more customer-centric. Thesesystems open the door to integrated loyalty programs and other customerrelationship management tools to help merchants know who their bestcustomers are and how to best reach them how, when and where thecustomer wants to shop.

Some embodiments of a system for unified inventory and financialtransaction management also allow developers to integrate payments,inventory and business insights into their platforms through the onlysingle stack of application program interfaces for card present and cardnot present transactions.

Some embodiments include a system for providing inventory managementservices from a plurality of disparate inventory resources fortransactions received from a plurality of disparate transaction intakeplatforms. In some embodiments, one or more computers configured toimplement executes instructions on one or more processors for aplatform-agnostic transaction-related communication system. In someembodiments, the transaction-related communication system includes oneor more receiving modules configured for receiving a first item ofinventory transaction information from a customer-facing interface, andreceiving a second item of inventory transaction information from amerchant-facing point-of-sale interface. In some embodiments, thetransaction-related communication system includes an inventorycoordination module configured for rendering in a common internal formatthe first item of inventory transaction information from thecustomer-facing interface, and rendering in the common internal formatthe second item of inventory transaction information from themerchant-facing point-of-sale interface. In some embodiments, thetransaction-related communication system includes an inventorycoordination module configured for transmitting the second item ofinventory transaction information for inventory transaction execution bythe second inventory resource, and transmitting the first item ofinventory transaction information for inventory transaction execution bya first inventory resource.

In some embodiments, the transaction-related communication systemincludes a synchronization server module configured for providingbackground updates of transactions to the customer facing interface andthe merchant-facing point of sale interface. In some embodiments, thereceiving the first item of inventory transaction information from thecustomer-facing interface further includes receiving in the commonintake transaction ticket format over the network from a mobilecomputing device an order for an item as the first item of inventorytransaction information from the customer-facing interface. In someembodiments, the receiving the second item of inventory transactioninformation from the merchant-facing point-of-sale interface furtherincludes receiving over the network in the common intake transactionticket format a return of the item as the second item of inventorytransaction information from the merchant-facing point-of-saleinterface. In some embodiments, the inventory coordination module isfurther configured for updating a unified inventory database to reflectfulfillment of the order for the item, and the inventory coordinationmodule is further configured for updating a unified inventory databaseto reflect fulfillment of the return of the item.

In some embodiments, the receiving the first item of inventorytransaction information from the customer-facing interface furtherincludes receiving in the common intake transaction ticket format overthe network from a mobile computing device an order for an item as thefirst item of inventory transaction information from the customer-facinginterface. In some embodiments, the receiving the second item ofinventory transaction information from the merchant-facing point-of-saleinterface further includes receiving over the network in the commonintake transaction ticket format a return of the item as the second itemof inventory transaction information from the merchant-facingpoint-of-sale interface. In some embodiments, the inventory coordinationmodule is further configured for querying a unified inventory databaseto ascertain whether fulfillment of the order for the item is possible,and the inventory coordination module is further configured for updatinga unified inventory database to reflect fulfillment of the return of theitem.

In some embodiments, the common internal format is a common intaketransaction ticket format, and the one or more receiving modules includea single stack application program interface residing on one of the oneor more servers.

In some embodiments, the receiving the first item of inventorytransaction information from the customer-facing interface furtherincludes receiving in the common intake transaction ticket format overthe network from a mobile computing device an order for an item as thefirst item of inventory transaction information from the customer-facinginterface. In some embodiments, the receiving the second item ofinventory transaction information from the merchant-facing point-of-saleinterface further includes receiving over the network in the commonintake transaction ticket format a return of the item as the second itemof inventory transaction information from the merchant-facingpoint-of-sale interface. In some embodiments, the inventory coordinationmodule is further configured for updating a unified inventory databaseto reflect fulfillment of the order for the item from an inventorywarehouse resource. In some embodiments, the inventory coordinationmodule is further configured for updating a unified inventory databaseto reflect fulfillment of the return of the item by updating an in-stockinventory count for a brick-and-mortar retail location housing themerchant-facing point-of-sale interface.

In some embodiments, the system further includes a business intelligenceanalytics module configured for providing business intelligence based atleast in part on the inventory transaction information.

Some embodiments include a method for providing inventory managementservices from a plurality of disparate inventory resources fortransactions received from a plurality of disparate transaction intakeplatforms. In some embodiments, the method includes one or morecomputers executing instructions on one or more processors for aplatform-agnostic transaction-related communication method.

In some embodiments, the method includes a receiving module receiving afirst item of inventory transaction information from a customer-facinginterface. In some embodiments, the method includes the receiving modulereceiving a second item of inventory transaction information from amerchant-facing point-of-sale interface. In some embodiments, the methodincludes an inventory coordination module rendering in a common internalformat the first item of inventory transaction information from thecustomer-facing interface. In some embodiments, the method includes theinventory coordination module rendering in the common internal formatthe second item of inventory transaction information from themerchant-facing point-of-sale interface. In some embodiments, the methodincludes the inventory coordination module transmitting the second itemof inventory transaction information for inventory transaction executionby the second inventory resource. In some embodiments, the methodincludes the inventory coordination module transmitting the first itemof inventory transaction information for inventory transaction executionby a first inventory resource.

In some embodiments, the method includes a synchronization server moduleproviding background updates of transactions to the customer facinginterface and the merchant-facing point of sale interface. In someembodiments, the receiving the first item of inventory transactioninformation from the customer-facing interface further includesreceiving in the common intake transaction ticket format over thenetwork from a mobile computing device an order for an item as the firstitem of inventory transaction information from the customer-facinginterface. In some embodiments, the receiving the second item ofinventory transaction information from the merchant-facing point-of-saleinterface further includes receiving over the network in the commonintake transaction ticket format a return of the item as the second itemof inventory transaction information from the merchant-facingpoint-of-sale interface. In some embodiments, the method furtherincludes updating a unified inventory database to reflect fulfillment ofthe order for the item, and the method further includes updating aunified inventory database to reflect fulfillment of the return of theitem.

In some embodiments, the receiving the first item of inventorytransaction information from the customer-facing interface furtherincludes receiving in the common intake transaction ticket format overthe network from a mobile computing device an order for an item as thefirst item of inventory transaction information from the customer-facinginterface. In some embodiments, the receiving the second item ofinventory transaction information from the merchant-facing point-of-saleinterface further includes receiving over the network in the commonintake transaction ticket format a return of the item as the second itemof inventory transaction information from the merchant-facingpoint-of-sale interface. In some embodiments, the method furtherincludes querying a unified inventory database to ascertain whetherfulfillment of the order for the item is possible, and the methodfurther includes updating a unified inventory database to reflectfulfillment of the return of the item.

In some embodiments, the common internal format is a common intaketransaction ticket format, and the one or more receiving modules includea single stack application program interface residing on one of the oneor more servers.

In some embodiments, the receiving the first item of inventorytransaction information from the customer-facing interface furtherincludes receiving in the common intake transaction ticket format overthe network from a mobile computing device an order for an item as thefirst item of inventory transaction information from the customer-facinginterface. In some embodiments, the receiving the second item ofinventory transaction information from the merchant-facing point-of-saleinterface further includes receiving over the network in the commonintake transaction ticket format a return of the item as the second itemof inventory transaction information from the merchant-facingpoint-of-sale interface.

In some embodiments, the method further includes updating a unifiedinventory database to reflect fulfillment of the order for the item froman inventory warehouse resource, and the method further includesupdating a unified inventory database to reflect fulfillment of thereturn of the item by updating an in-stock inventory count for abrick-and-mortar retail location housing the merchant-facingpoint-of-sale interface.

In some embodiments, the method further includes a business intelligenceanalytics module providing business intelligence based at least in parton the inventory transaction information.

Some embodiments include a non-transitory computer-readable storagemedium storing program instructions for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms, wherein the programinstructions are computer-executable to implement a receiving modulereceiving a first item of inventory transaction information from acustomer-facing interface and the receiving module receiving a seconditem of inventory transaction information from a merchant-facingpoint-of-sale interface. In some embodiments, the program instructionsare computer-executable to implement an inventory coordination modulerendering in a common internal format the first item of inventorytransaction information from the customer-facing interface. In someembodiments, the program instructions are computer-executable toimplement the inventory coordination module rendering in the commoninternal format the second item of inventory transaction informationfrom the merchant-facing point-of-sale interface. In some embodiments,the program instructions are computer-executable to implement theinventory coordination module transmitting the second item of inventorytransaction information for inventory transaction execution by thesecond inventory resource. In some embodiments, the program instructionsare computer-executable to implement the inventory coordination moduletransmitting the first item of inventory transaction information forinventory transaction execution by a first inventory resource.

In some embodiments, the program instructions computer executable toimplement receiving the first item of inventory transaction informationfrom the customer-facing interface further include program instructionscomputer executable to implement receiving in the common intaketransaction ticket format over the network from a mobile computingdevice an order for an item as the first item of inventory transactioninformation from the customer-facing interface. In some embodiments, theprogram instructions computer executable to implement receiving thesecond item of inventory transaction information from themerchant-facing point-of-sale interface further include programinstructions computer executable to implement receiving over the networkin the common intake transaction ticket format a return of the item asthe second item of inventory transaction information from themerchant-facing point-of-sale interface.

In some embodiments, the non-transitory computer readable storage mediumfurther includes program instructions computer executable to implementupdating a unified inventory database to reflect fulfillment of theorder for the item, and the non-transitory computer readable storagemedium further includes program instructions computer executable toimplement updating a unified inventory database to reflect fulfillmentof the return of the item.

In some embodiments, the program instructions computer executable toimplement receiving the first item of inventory transaction informationfrom the customer-facing interface further include program instructionscomputer executable to implement receiving in the common intaketransaction ticket format over the network from a mobile computingdevice an order for an item as the first item of inventory transactioninformation from the customer-facing interface. In some embodiments, theprogram instructions computer executable to implement receiving thesecond item of inventory transaction information from themerchant-facing point-of-sale interface further include programinstructions computer executable to implement receiving over the networkin the common intake transaction ticket format a return of the item asthe second item of inventory transaction information from themerchant-facing point-of-sale interface.

In some embodiments, the non-transitory computer readable storage mediumfurther includes program instructions computer executable to implementquerying a unified inventory database to ascertain whether fulfillmentof the order for the item is possible, and the non-transitory computerreadable storage medium further includes program instructions computerexecutable to implement updating a unified inventory database to reflectfulfillment of the return of the item. In some embodiments, the commoninternal format is a common intake transaction ticket format, and theone or more receiving modules include a single stack application programinterface residing on one of the one or more servers.

In some embodiments, the program instructions computer executable toimplement receiving the first item of inventory transaction informationfrom the customer-facing interface further include program instructionscomputer executable to implement receiving in the common intaketransaction ticket format over the network from a mobile computingdevice an order for an item as the first item of inventory transactioninformation from the customer-facing interface.

In some embodiments, the program instructions computer executable toimplement receiving the second item of inventory transaction informationfrom the merchant-facing point-of-sale interface further include programinstructions computer executable to implement receiving over the networkin the common intake transaction ticket format a return of the item asthe second item of inventory transaction information from themerchant-facing point-of-sale interface.

In some embodiments, the non-transitory computer readable storage mediumfurther includes program instructions computer executable to implementupdating a unified inventory database to reflect fulfillment of theorder for the item from an inventory warehouse resource.

In some embodiments, the non-transitory computer readable storage mediumfurther includes program instructions computer executable to implementupdating a unified inventory database to reflect fulfillment of thereturn of the item by updating an in-stock inventory count for abrick-and-mortar retail location housing the merchant-facingpoint-of-sale interface.

In some embodiments, the system includes a processor and programinstructions computer-executable to implement a system for providingpayment processing services from a plurality of disparate paymentprocessors to a plurality of disparate transaction intake platforms. Insome embodiments, the system includes one or more computers configuredto implement by executing instructions on one or more processors aplatform-agnostic transaction-related communication system. In someembodiments, the transaction-related communication system includes oneor more receiving modules for receiving a first item of financialtransaction information from a customer-facing interface, and receivinga second item of financial transaction information from amerchant-facing point-of-sale interface.

In some embodiments, the transaction-related communication systemincludes a point of sale server for rendering in a common internalformat the first item of financial transaction information from thecustomer-facing interface, and rendering in the common internal formatthe second item of financial transaction information from themerchant-facing point-of-sale interface. In some embodiments, thetransaction-related communication system includes a payment processingmodule configured for rendering in a second format the first item offinancial transaction information for payment processing by a firstexternal financial party, and rendering in a third format the first itemof financial transaction information for payment processing by a secondexternal financial party.

In some embodiments, the transaction-related communication systemincludes a transaction execution module configured for transmitting inthe second format the first item of financial transaction informationfor payment processing by the first external financial party, andtransmitting in the third format the second item of financialtransaction information for payment processing by the second externalfinancial party.

In some embodiments, the system supports providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms. In some embodiments, thecommon internal format is a common intake transaction ticket format. Insome embodiments, the one or more receiving modules include a singlestack application program interface residing on one of the one or moreservers. In some embodiments, the receiving the first item of financialtransaction information from the customer-facing interface furtherincludes receiving in the common intake transaction ticket format overthe network from a mobile computing device the first item of financialtransaction information from the customer-facing interface. In someembodiments, the receiving the second item of financial transactioninformation from the merchant-facing point-of-sale interface furtherincludes receiving over the network in the common intake transactionticket format the second item of financial transaction information fromthe merchant-facing point-of-sale interface.

In some embodiments, the common internal format is a common intaketransaction ticket format. In some embodiments, the system furtherincludes a first translation module on a mobile computing device forreceiving from a customer facing application including thecustomer-facing interface on the mobile computing device the first itemof financial transaction information, and translating to a common intaketransaction ticket format the first item of financial transactioninformation. In some embodiments, the system further includes a secondtranslation module on a merchant-facing point of sale device forreceiving from a merchant facing application including themerchant-facing point-of-sale interface on a merchant point of saledevice the second item of financial transaction information, andtranslating to the common intake transaction ticket format the seconditem of financial transaction information.

In some embodiments, the one or more receiving modules include a singlestack application program interface residing on one of the one or moreservers. In some embodiments, the server communicates remotely with themobile computing device over a wireless network. In some embodiments,the server communicates remotely with the merchant-facing point of saledevice over a second network. In some embodiments, the receiving thefirst item of financial transaction information from the customer-facinginterface further includes receiving in the common intake transactionticket format at the single stack application interface from the mobilecomputing device the first item of financial transaction informationfrom the customer-facing interface. In some embodiments, the receivingthe second item of financial transaction information from themerchant-facing point-of-sale interface further includes receiving inthe common intake transaction ticket format at the single stackapplication interface the second item of financial transactioninformation from the merchant-facing point-of-sale interface.

In some embodiments, the transaction execution module is furtherconfigured for receiving on the one or more servers a transactionauthorization confirmation from the first external financial party, andthe point of sale server is further configured for transmitting to thecustomer-facing interface an indication of the transaction authorizationconfirmation. In some embodiments, the payment processing moduleincludes a payment processing gateway for communicating with servers ofexternal financial processors using encrypted links over a network.

In some embodiments, the system for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms further includes a businessintelligence analytics module configured for providing businessintelligence based at least in part on the first item of financialtransaction information.

In some embodiments, the system for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms further includes an inventorycoordination module configured for providing transaction fulfillmentinformation based at least in part on the first item of financialtransaction information.

Some embodiments include a method for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms. In some embodiments, themethod includes causing modules, implemented as hardware, software, or acombination of hardware and software on one or more computers executinginstructions on one or more processors to implement a platform-agnostictransaction-related communication system that performs a methodincluding receiving a first item of financial transaction informationfrom a customer-facing interface and receiving a second item offinancial transaction information from a merchant-facing point-of-saleinterface.

In some embodiments, the method includes rendering in a common internalformat the first item of financial transaction information from thecustomer-facing interface. In some embodiments, the method includesrendering in the common internal format the second item of financialtransaction information from the merchant-facing point-of-saleinterface. In some embodiments, the method includes rendering in asecond format the first item of financial transaction information forpayment processing by a first external financial party. In someembodiments, the method includes rendering in a third format the firstitem of financial transaction information for payment processing by asecond external financial party.

In some embodiments, the method includes transmitting in the secondformat the first item of financial transaction information for paymentprocessing by the first external financial party. In some embodiments,the method includes transmitting in the third format the second item offinancial transaction information for payment processing by the secondexternal financial party.

In some embodiments, the method includes providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms. In some embodiments, thecommon internal format is a common intake transaction ticket format.

In some embodiments, the receiving the first item of financialtransaction information from the customer-facing interface furtherincludes receiving in the common intake transaction ticket format overthe network from a mobile computing device the first item of financialtransaction information from the customer-facing interface. In someembodiments, the receiving the second item of financial transactioninformation from the merchant-facing point-of-sale interface furtherincludes receiving over the network in the common intake transactionticket format the second item of financial transaction information fromthe merchant-facing point-of-sale interface.

In some embodiments, the common internal format is a common intaketransaction ticket format, and the method further includes receivingfrom a customer facing application including the customer-facinginterface on the mobile computing device the first item of financialtransaction information. In some embodiments, the common internal formatis a common intake transaction ticket format, and the method furtherincludes translating to a common intake transaction ticket format thefirst item of financial transaction information. In some embodiments,the common internal format is a common intake transaction ticket format,and the method further includes receiving from a merchant facingapplication including the merchant-facing point-of-sale interface on amerchant point of sale device the second item of financial transactioninformation. In some embodiments, the common internal format is a commonintake transaction ticket format, and the method further includestranslating to the common intake transaction ticket format the seconditem of financial transaction information.

In some embodiments, the receiving the first item of financialtransaction information from the customer-facing interface furtherincludes receiving in the common intake transaction ticket format at asingle stack application interface from the mobile computing device thefirst item of financial transaction information from the customer-facinginterface. In some embodiments, the receiving the second item offinancial transaction information from the merchant-facing point-of-saleinterface further includes receiving in the common intake transactionticket format at the single stack application interface the second itemof financial transaction information from the merchant-facingpoint-of-sale interface.

In some embodiments, the method further includes receiving on the one ormore servers a transaction authorization confirmation from the firstexternal financial party, and transmitting to the customer-facinginterface an indication of the transaction authorization confirmation.In some embodiments, the method further includes a payment processinggateway communicating with servers of external financial processorsusing encrypted links over a network. In some embodiments, the methodfurther includes a business intelligence analytics module providingbusiness intelligence based at least in part on the first item offinancial transaction information.

In some embodiments, the method further includes an inventorycoordination module providing transaction fulfillment information basedat least in part on the first item of financial transaction information.

Some embodiments include a non-transitory computer-readable storagemedium storing program instructions for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms. In some embodiments, theprogram instructions are computer-executable to implement receiving afirst item of financial transaction information from a customer-facinginterface. In some embodiments, the program instructions arecomputer-executable to implement receiving a second item of financialtransaction information from a merchant-facing point-of-sale interface.In some embodiments, the program instructions are computer-executable toimplement rendering in a common internal format the first item offinancial transaction information from the customer-facing interface. Insome embodiments, the program instructions are computer-executable toimplement rendering in the common internal format the second item offinancial transaction information from the merchant-facing point-of-saleinterface.

In some embodiments, the program instructions are computer-executable toimplement transmitting in the second format the first item of financialtransaction information for payment processing by the first externalfinancial party. In some embodiments, the program instructions arecomputer-executable to implement transmitting in the third format thesecond item of financial transaction information for payment processingby the second external financial party.

In some embodiments, the common internal format is a common intaketransaction ticket format. In some embodiments, the program instructionscomputer-executable to implement receiving the first item of financialtransaction information from the customer-facing interface furtherinclude program instructions computer-executable to implement receivingin the common intake transaction ticket format over the network from amobile computing device the first item of financial transactioninformation from the customer-facing interface. In some embodiments, theprogram instructions computer-executable to implement receiving thesecond item of financial transaction information from themerchant-facing point-of-sale interface further include programinstructions computer-executable to implement receiving over the networkin the common intake transaction ticket format the second item offinancial transaction information from the merchant-facing point-of-saleinterface.

In some embodiments, the common internal format is a common intaketransaction ticket format. In some embodiments, the program instructionscomputer-executable for providing payment processing services furtherinclude program instructions computer-executable to implement receivingfrom a customer facing application including the customer-facinginterface on the mobile computing device the first item of financialtransaction information. In some embodiments, the program instructionscomputer-executable for providing payment processing services furtherinclude program instructions computer-executable to implementtranslating to a common intake transaction ticket format the first itemof financial transaction information. In some embodiments, the programinstructions for providing payment processing services further includeprogram instructions computer-executable to implement receiving from amerchant facing application including the merchant-facing point-of-saleinterface on a merchant point of sale device the second item offinancial transaction information. In some embodiments, the programinstructions for providing payment processing services further includeprogram instructions computer-executable to implement translating to thecommon intake transaction ticket format the second item of financialtransaction information.

In some embodiments, the one or more receiving modules include a singlestack application program interface residing on one of the one or moreservers. In some embodiments, the program instructionscomputer-executable to implement receiving the first item of financialtransaction information from the customer-facing interface furtherinclude program instructions computer-executable to implement receivingin the common intake transaction ticket format at the single stackapplication interface from the mobile computing device the first item offinancial transaction information from the customer-facing interface. Insome embodiments, the program instructions computer-executable toimplement receiving the second item of financial transaction informationfrom the merchant-facing point-of-sale interface further include programinstructions computer-executable to implement receiving in the commonintake transaction ticket format at the single stack applicationinterface the second item of financial transaction information from themerchant-facing point-of-sale interface.

In some embodiments, the program instructions for providing paymentprocessing services further include program instructionscomputer-executable to implement receiving on the one or more servers atransaction authorization confirmation from the first external financialparty, and program instructions computer-executable to implementtransmitting to the customer-facing interface an indication of thetransaction authorization confirmation. In some embodiments, the programinstructions for providing payment processing services further includeprogram instructions computer-executable to implement further includeprogram instructions computer-executable to implement a paymentprocessing gateway for communicating with servers of external financialprocessors using encrypted links over a network.

In some embodiments, the program instructions for providing paymentprocessing services further include program instructionscomputer-executable to implement program instructionscomputer-executable to implement a business intelligence analyticsmodule configured for providing business intelligence based at least inpart on the first item of financial transaction information. In someembodiments, the program instructions for providing payment processingservices further include program instructions computer-executable toimplement program instructions computer-executable to implement aninventory coordination module configured for transaction fulfillmentinformation based at least in part on the first item of financialtransaction information.

Example Implementations

FIG. 1 depicts a distributed system that may implement a wireless datacommunication interface, according to some embodiments. An integratedelectronic commerce management provider 100 hosts a system 198 forproviding payment processing services from a plurality of disparatepayment processors 151-156 to a plurality of disparate transactionintake platforms 118, 110 and 110. Integrated electronic commercemanagement provider 100 includes, in some embodiments, a database 101storing electronic commerce inventory and transaction records in acommon internal format. Integrated electronic commerce managementprovider 100 includes, in some embodiments, an integrated wirelesscommerce module 120 for implementing platform-agnostictransaction-related communication across a single-stack standardapplication program interface gateway 106. An ordering customer clientembodied in the form of a customer mobile device 110, a merchant clientembodied in the form of a cash register or other form of merchant-facingpoint of sale hardware 110, a customer web browser 118, paymentprocessors 151-156, a point of sale location embodied as abrick-and-mortar store 160, an inventory resource embodied as afulfillment warehouse 170, and another point of sale location embodiedas a brick-and-mortar store 180 communicate across network 150 withintegrated wireless commerce module 120 to implement platform-agnostictransaction-related communication using single-stack standardapplication program interface gateway 106.

On customer mobile device 110, a customer-facing an order interfaceembodied as a customer-facing mobile point of sale application 111undertakes transaction communications 114 with single-stack standardapplication program interface gateway 106 over network 150. On customerweb browser 118 (e.g., executing on a desktop PC), a customer-facing anorder interface embodied as a customer-facing web interface 116undertakes transaction communications 115 with single-stack standardapplication program interface gateway 106 over network 150. Onmerchant-facing point-of-sale hardware client 110, a merchant point ofsale interface 111 undertakes transaction communications 114 withsingle-stack standard application program interface gateway 106 overnetwork 150. Payment processors 151-156 undertake transactioncommunications 164-168 with single-stack standard application programinterface gateway 106 over network 150. In some embodiments, wirelesstransaction communications 196 are undertaken between customer mobiledevice 110 and merchant-facing point of sale hardware 110 to automatecreation of transactions.

In some embodiments, integrated electronic commerce management provider100 provides a system for providing a wireless data communicationinterface. In some embodiments, the system 198 includes one or morecomputers, such as will be discussed below with respect to FIG. 36 ,configured to implement by executing instructions on one or moreprocessors to provide a platform-agnostic wireless data communicationsystem. In some embodiments, an integrated wireless commerce module 120includes one or more receiving modules for receiving over a wirelessdata communication channel (as part of transaction communications 114) atokenized first item of financial transaction information from acustomer mobile device 110 presenting a customer-facing interface (e.g.,customer facing mobile POS app 111), and receiving (as part oftransaction communications 114) a second item of financial transactioninformation from a merchant-facing point-of-sale interface connected tothe mobile device through the wireless data communication channel.

In some embodiments, integrated wireless commerce module 120 provides apoint of sale server for rendering in a common internal format the firstitem of financial transaction information from the customer-facinginterface (e.g., from customer-facing mobile POS app 111), and renderingin the common internal format the second item of financial transactioninformation from the merchant-facing point-of-sale interface (e.g.,merchant POS interface 111).

In some embodiments, integrated wireless commerce module 120 provides apayment processing module for rendering in a second format the firstitem of financial transaction information for payment processing by afirst external financial party (e.g., one of payment processors151-156). In some embodiments, the rendering in the second formatincludes converting the tokenized first item of financial transactioninformation to an account-specific item of financial transactioninformation using an account identifier associated with the tokenizedfirst item in a registry stored in a secured account data vault, andrendering in a third format the second item of financial transactioninformation for payment processing by a second external financial party(e.g., one of payment processors 151-156).

In some embodiments, integrated wireless commerce module 120 provides atransaction execution module for transmitting in the second format thefirst item of financial transaction information for payment processingby the first external financial party (e.g., one of payment processors151-156). In some embodiments, the second format includes the financialtransaction information using the account identifier associated with thetokenized first item in a registry stored in a secured account datavault. In some embodiments, the transaction execution module is furtherconfigured for transmitting in the third format the second item offinancial transaction information for payment processing by the secondexternal financial party.

In some embodiments, integrated wireless commerce module 120 provides anauthentication module for recognizing a customer mobile device (e.g.,customer mobile device 110 hosting customer-facing mobile POS app 111)located in an area defined within a geofence, identifying a customerassociated with the customer mobile device 110 based at least in part ona presence of an application (e.g., customer-facing mobile POS app 111)executing on the customer mobile device, and issuing a session token tothe application on the customer mobile device 110.

In some embodiments, the transmitting in the second format the firstitem of financial transaction information for payment processing by thefirst external financial party (e.g., one of payment processors 151-156)in the second format further includes transmitting in the second formatthe first item of financial transaction information for paymentprocessing by the first external financial party. In some embodiments,the transmitting financial transaction information using the accountidentifier associated with the tokenized first item in a registry storedin the secured account data vault without transmitting the financialtransaction information using the account identifier associated with thetokenized first item in the registry stored in the secured account datavault to the merchant-facing point-of-sale interface.

In some embodiments, the receiving over a wireless data communicationchannel a tokenized first item of financial transaction information froma customer mobile device (e.g., customer mobile device 110 hostingcustomer-facing mobile POS app 111) presenting a customer-facinginterface (e.g., customer-facing mobile POS app 111) further includesreceiving over a Bluetooth low energy radio communication channel atokenized first item of financial transaction information from acustomer mobile device presenting a customer-facing interface.

In some embodiments, the receiving a second item of financialtransaction information from a merchant-facing point-of-sale interface(e.g., merchant POS interface 111) connected to the mobile devicethrough the wireless data communication channel 196 further includesreceiving over a broadband wireless network a second item of financialtransaction information from a merchant-facing point-of-sale interface(e.g., merchant POS interface 111) connected to the mobile device (e.g.,customer mobile device 110 hosting customer-facing mobile POS app 111)through the wireless data communication channel 196.

In some embodiments, the one or more receiving modules include a singlestack application program interface 106 residing on one of the one ormore servers.

In some embodiments, the transaction execution module is furtherconfigured for receiving on the one or more servers a transactionauthorization confirmation from the first external financial party(e.g., one of payment processors 151-156).

In some embodiments, the point of sale server is further configured fortransmitting to the customer-facing interface (e.g., customer mobiledevice 110 hosting customer-facing mobile POS app 111) an indication ofthe transaction authorization confirmation.

In some embodiments, the payment processing module includes a paymentprocessing gateway (e.g., single stack application program interface106) for communicating with servers of external financial processors(e.g., one of payment processors 151-156) using encrypted links over anetwork.

In some embodiments, inventory transactions can be reported by orordered by transaction communication 104 a-104 n over network 150 topoint of sale client 161, inventory client 171, and point of sale client181. In some embodiments, inventory transactions involve the delivery194 or return 191 of delivery goods 190. Likewise, inventorytransactions involve the transfer 184 from a first point of salelocation in the form of second brick and mortar store 180 to a secondpoint of sale location in the form of first brick and mortar store 160or the transfer 174 from an inventory resource in the form offulfillment warehouse 170 to a point of sale location in the form offirst brick and mortar store 160.

In some embodiments, the system 198 includes one or more computers, suchas will be discussed below with respect to FIG. 36 , configured toimplement by executing instructions on one or more processors aplatform-agnostic transaction-related communication system. In someembodiments, the transaction-related communication system includes oneor more receiving modules, which can, in some example embodiments, belocated in or executing on customer web browser 118, customer mobiledevice 110, merchant facing point of sale hardware 110, or integratedelectronic commerce module 104, for receiving a first item of financialtransaction information from a customer-facing interface (for example,in some embodiments customer facing mobile point of sale application 111or customer facing web interface 116), and receiving a second item offinancial transaction information from a merchant-facing point-of-saleinterface (for example, in some embodiments merchant point of saleinterface 111). As one of skill in the art will readily comprehend inlight of having read the present disclosure, any function described ashaving been performed by a module or interface of the present disclosurecan be performed by another interface or module of the presentdisclosure without departing from the scope and intent of the presentdisclosure.

In some embodiments, the transaction-related communication systemincludes a point of sale server (for example, in some embodimentslocated in customer mobile device 110) for rendering in a commoninternal format the first item of financial transaction information fromthe customer-facing interface (for example, in some embodiments customerfacing mobile point of sale application 111), and rendering in thecommon internal format the second item of financial transactioninformation from the merchant-facing point-of-sale interface (forexample, in some embodiments merchant point of sale interface 111). Insome embodiments, the transaction-related communication system includesa payment processing module (for example, in some embodiments, containedwithin integrated electronic commerce module 104), for rendering in asecond format the first item of financial transaction information forpayment processing by a first external financial party (for example, insome embodiments payment processor 151), and rendering in a third formatthe first item of financial transaction information for paymentprocessing by a second external financial party (for example, in someembodiments payment processor 154).

In some embodiments, the transaction-related communication systemincludes a transaction execution module (for example, in someembodiments, contained within integrated electronic commerce module104), for transmitting in the second format the first item of financialtransaction information for payment processing by the first externalfinancial party (for example, in some embodiments payment processor151), and transmitting in the third format the second item of financialtransaction information for payment processing by the second externalfinancial party (for example, in some embodiments payment processor154).

In some embodiments, the system provides payment processing servicesfrom a plurality of disparate payment processors (for example, in someembodiments, payment processors 151-156) to a plurality of disparatetransaction intake platforms (for example, in some embodiments customermobile device 110 and merchant facing point of sale hardware 110). Insome embodiments, the common internal format is a common intaketransaction ticket format. In some embodiments, the one or morereceiving modules include a single stack application program interfaceresiding on one of the one or more servers (for example, in someembodiments as a part of single-stack standard application programminginterface gateway 106). In some embodiments, the receiving the firstitem of financial transaction information from the customer-facinginterface (for example, in some embodiments customer facing mobile pointof sale application 111) further includes receiving in the common intaketransaction ticket format over the network from a mobile computingdevice (for example, in some embodiments customer mobile device 110 orcustomer web browser 118) the first item of financial transactioninformation from the customer-facing interface (for example, in someembodiments customer facing mobile point of sale application 111). Insome embodiments, the receiving the second item of financial transactioninformation from the merchant-facing point-of-sale interface (forexample, in some embodiments merchant point of sale interface 111)further includes receiving over the network in the common intaketransaction ticket format the second item of financial transactioninformation from the merchant-facing point-of-sale interface (forexample, in some embodiments merchant facing point of sale hardware110).

In some embodiments, the common internal format is a common intaketransaction ticket format. In some embodiments, the system furtherincludes a first translation module on a mobile computing device (forexample, in some embodiments customer mobile device 110) for receivingfrom a customer facing application including the customer-facinginterface (for example, in some embodiments customer facing mobile pointof sale application 111) on the mobile computing device the first itemof financial transaction information, and translating to a common intaketransaction ticket format the first item of financial transactioninformation. In some embodiments, the system further includes a secondtranslation module on a merchant-facing point of sale device (forexample, in some embodiments merchant facing point of sale hardware 110)for receiving from a merchant facing application (for example, in someembodiments merchant point of sale interface 111) including themerchant-facing point-of-sale interface on a merchant point of saledevice the second item of financial transaction information, andtranslating to the common intake transaction ticket format the seconditem of financial transaction information.

In some embodiments, the one or more receiving modules include a singlestack application program interface residing on one of the one or moreservers. In some embodiments, the server (for example, in someembodiments integrated electronic commerce module 104) communicates (forexample, in some embodiments sending and receiving communications 114)remotely with the mobile computing device (for example, in someembodiments customer mobile device 110) over a wireless network (forexample, in some embodiments network 150). In some embodiments, theserver (for example, in some embodiments integrated electronic commercemodule 104) communicates remotely with the merchant-facing point of saledevice over a second network. In some embodiments, the receiving thefirst item of financial transaction information from the customer-facinginterface (for example, in some embodiments in customer facing mobilepoint of sale application 111) further includes receiving in the commonintake transaction ticket format at the single stack applicationinterface (for example, in some embodiments in single-stack standardapplication programming interface gateway 106) from the mobile computingdevice the first item of financial transaction information from thecustomer-facing interface (for example, in some embodiments incustomer-facing mobile point of sale application 111). In someembodiments, the receiving the second item of financial transactioninformation from the merchant-facing point-of-sale interface furtherincludes receiving in the common intake transaction ticket format at thesingle stack application interface (for example, in some embodiments insingle-stack standard application programming interface gateway 106) thesecond item of financial transaction information from themerchant-facing point-of-sale interface (for example, in someembodiments merchant point of sale interface 111).

In some embodiments, the transaction execution module (for example, insome embodiments in integrated electronic commerce module 104) isfurther configured for receiving on the one or more servers atransaction authorization confirmation from the first external financialparty, and the point of sale server (for example, in some embodiments inintegrated electronic commerce module 104) is further configured fortransmitting to the customer-facing interface (for example, in someembodiments customer facing mobile point of sale application 111) anindication of the transaction authorization confirmation. In someembodiments, the payment processing module includes a payment processinggateway (for example, in some embodiments in single-stack standardapplication programming interface gateway 106) for communicating withservers of external financial processors (for example, in someembodiments payment processors 151-156) using encrypted links over anetwork 150.

In some embodiments, the system for providing payment processingservices from a plurality of disparate payment processors (for example,in some embodiments payment processors 151-156) to a plurality ofdisparate transaction intake platforms further includes a businessintelligence analytics module (for example, in some embodiments inintegrated electronic commerce module 104) for providing businessintelligence based at least in part on the first item of financialtransaction information.

In some embodiments, the system for providing payment processingservices from a plurality of disparate payment processors (for example,in some embodiments payment processors 151-156) to a plurality ofdisparate transaction intake platforms (for example, in some embodimentsmerchant facing point of sale hardware 110 and customer mobile device110) further includes an inventory coordination module (for example, insome embodiments in integrated electronic commerce module 104) forproviding transaction fulfillment information based at least in part onthe first item of financial transaction information.

In some embodiments, the inventory coordination module enables theintegrated electronic commerce module 104 to monitor consolidated stocklevels and determine when to re-order, without relying on additionalsystems or manual reporting, thereby enabling merchants to provide aconsistent, seamless experience for consumers across all channels,including offering returns through any channel no matter where thepurchase originated.

Some embodiments of integrated electronic commerce module 104 support amerchant that operates a physical store, operates an online store, andaccepts payments on a mobile device, or any combination of thosechannels. Some embodiments of integrated electronic commerce module 104present a single merchant account to reduce reconciliation andaccounting headaches and to provide one version of the data throughconsolidated reports across all channels and touchpoints. Someembodiments of integrated electronic commerce module 104 can also handlethe issues of managing inventory across mobile and e-commercetouchpoints, as well as in the store, providing a single view of themerchandise that's available to sell, and helping businesses balancebetween inventory and demand.

Some embodiments of integrated electronic commerce module 104 support acloud-based point-of-sale, mobile and eCommerce framework thatintegrates payments with inventory management.

Some embodiments of integrated electronic commerce module 104 real-time,in-app inventory tracking, management and replenishment directly from amobile application. Some embodiments of integrated electronic commercemodule 104 provide import and export capabilities that allow merchantsto easily transfer and integrate inventory data into other systems. Someembodiments of integrated electronic commerce module 104 provideIntegration with third party eCommerce platforms—sales and inventorydata by location provides merchants more valuable insights into theirbusiness. Some embodiments of integrated electronic commerce module 104provide the ability to set replenishment thresholds and alerts andtransfer inventory between locations and channels. Some embodiments ofintegrated electronic commerce module 104 adjust inventory for sales andreturns in real-time and can also work with a merchant's existinginventory platform, by allowing merchants to integrate in to someembodiments of integrated electronic commerce module 104 usingapplication program interfaces.

Some embodiments of integrated electronic commerce module 104 can alsosolve the problems of the friction points mentioned above by eliminatingdisparate payment processors and processing rates, further simplifyingreconciliation across all of a merchant's selling channels. In moving toa single payments provider under some embodiments, merchants can alsotake advantage of volume pricing, and get the best possible rates foreach channel.

Some embodiments of integrated electronic commerce module 104 providebusiness insights, such merchants can leverage data to optimize sales,for example such as how much floor space to allocate to specificproducts, what items and locations provide the most revenue and profitand what products to feature. Merchants also have the ability to storecustomer history, past purchases and other customer-specific data tohelp them become more customer-centric. These systems open the door tointegrated loyalty programs and other customer relationship managementtools to help merchants know who their best customers are and how tobest reach them how, when and where the customer wants to shop.

Some embodiments of integrated electronic commerce module 104 also allowdevelopers to integrate payments, inventory and business insights intotheir platforms through the only single stack of application programinterfaces for card present and card not present transactions.

Some embodiments of integrated electronic commerce module 104 alsoinclude a system for providing inventory management services from aplurality of disparate inventory resources (for example, in someembodiments brick-and-mortar store 160, fulfillment warehouse 170 andbrick and mortar store 180) for transactions received from a pluralityof disparate transaction intake platforms (for example, in someembodiments customer web browser 118, customer mobile device 110 andmerchant facing point of sale hardware 110).

In some embodiments, one or more computers executes instructions on oneor more processors for a platform-agnostic transaction-relatedcommunication system 198. In some embodiments, the transaction-relatedcommunication system includes one or more receiving modules, which can,in some example embodiments, be located in brick-and-mortar store 160,fulfillment warehouse 170 and brick and mortar store 180, customer webbrowser 118, customer mobile device 110 and merchant facing point ofsale hardware 110 configured for receiving a first item of inventorytransaction information from a customer-facing interface such ascustomer mobile device 110, and receiving a second item of inventorytransaction information from a merchant-facing point-of-sale interface,such as merchant facing point of sale hardware 110.

In some embodiments, the transaction-related communication systemincludes an inventory coordination module (for example, in someembodiments, contained within integrated electronic commerce module104), configured for rendering in a common internal format the firstitem of inventory transaction information from the customer-facinginterface (for example, in some embodiments customer facing mobile pointof sale application 111), and rendering in the common internal formatthe second item of inventory transaction information from themerchant-facing point-of-sale interface (for example, in someembodiments, merchant point of sale interface 111). In some embodiments,the transaction-related communication system includes an inventorycoordination module configured for transmitting the second item ofinventory transaction information for inventory transaction execution bythe second inventory resource (for example, in some embodiments, awarehouse or manufacturing facility, such as fulfillment warehouse 170),and transmitting the first item of inventory transaction information forinventory transaction execution by a first inventory resource (forexample, in some embodiments, brick and mortar store 160).

In some embodiments, the transaction-related communication systemincludes a synchronization server module (for example, in someembodiments, contained within integrated electronic commerce module 104)configured for providing background updates of transactions to thecustomer facing interface and the merchant-facing point of saleinterface (for example, in some embodiments customer-facing web browser118 customer mobile device 110 and merchant facing point of salehardware 110). In some embodiments, the receiving the first item ofinventory transaction information from the customer-facing interfacefurther includes receiving in the common intake transaction ticketformat over the network from a mobile computing device an order for anitem as the first item of inventory transaction information from thecustomer-facing interface (for example, in some embodiments customermobile device 110). In some embodiments, the receiving the second itemof inventory transaction information from the merchant-facingpoint-of-sale interface further includes receiving over the network inthe common intake transaction ticket format a return of the item as thesecond item of inventory transaction information from themerchant-facing point-of-sale interface (for example, in someembodiments merchant facing point of sale hardware 110). In someembodiments, the inventory coordination module is further configured forupdating a unified inventory database (for example, in some embodimentsdatabase 101) to reflect fulfillment of the order for the item, and theinventory coordination module is further configured for updating aunified inventory database (for example, in some embodiments database101) to reflect fulfillment of the return of the item.

In some embodiments, the receiving the first item of inventorytransaction information from the customer-facing interface (for example,in some embodiments customer mobile device 110) further includesreceiving in the common intake transaction ticket format over thenetwork from a mobile computing device an order for an item as the firstitem of inventory transaction information from the customer-facinginterface (for example, in some embodiments customer facing mobile pointof sale application 111). In some embodiments, the receiving the seconditem of inventory transaction information from the merchant-facingpoint-of-sale interface (for example, in some embodiments merchantfacing point of sale hardware 110) further includes receiving over thenetwork in the common intake transaction ticket format a return of theitem as the second item of inventory transaction information from themerchant-facing point-of-sale interface (for example, in someembodiments merchant point of sale interface 111). In some embodiments,the inventory coordination module is further configured for querying aunified inventory database (for example, in some embodiments database101) to ascertain whether fulfillment of the order for the item ispossible, and the inventory coordination module is further configuredfor updating a unified inventory database (for example, in someembodiments database 101) to reflect fulfillment of the return of theitem.

In some embodiments, the common internal format is a common intaketransaction ticket format, and the one or more receiving modules includea single stack application program interface residing on one of the oneor more servers, such as single stack standard application programinterface gateway 106.

In some embodiments, the receiving the first item of inventorytransaction information from the customer-facing interface furtherincludes receiving in the common intake transaction ticket format overthe network from a mobile computing device (for example, in someembodiments customer mobile device 110) an order for an item as thefirst item of inventory transaction information from the customer-facinginterface (for example, in some embodiments merchant point of saleinterface 111). In some embodiments, the receiving the second item ofinventory transaction information from the merchant-facing point-of-saleinterface (for example, in some embodiments merchant facing point ofsale hardware 110) further includes receiving over the network in thecommon intake transaction ticket format a return of the item as thesecond item of inventory transaction information from themerchant-facing point-of-sale interface (for example, in someembodiments merchant facing point of sale hardware 110). In someembodiments, the inventory coordination module is further configured forupdating a unified inventory database (for example, in some embodimentsdatabase 101) to reflect fulfillment of the order for the item from aninventory warehouse resource. In some embodiments, the inventorycoordination module is further configured for updating a unifiedinventory database (for example, in some embodiments database 101) toreflect fulfillment of the return of the item by updating an in-stockinventory count for a brick-and-mortar retail location (for example, insome embodiments brick and mortar store 180) housing the merchant-facingpoint-of-sale interface (for example, in some embodiments point of saleclient 181).

In some embodiments, the system further includes a business intelligenceanalytics module (for example, in some embodiments, contained withinintegrated electronic commerce module 104) configured for providingbusiness intelligence based at least in part on the inventorytransaction information.

FIG. 2A illustrates a module that may implement a wireless datacommunication interface, according to some embodiments. An integratedwireless commerce management module 220 receives as input transactionexecution confirmations 270, transaction tickets 210 and user input 212(for example, in some embodiments, through a user interface 222) andstores transaction execution orders 250, unified inventory data 220, andunified format transactions 260 in a storage medium 240. Integratedwireless commerce management module 220 is one embodiment of integratedwireless commerce module 104 of FIG. 1 , which is discussed above.

In some embodiments, integrated wireless commerce management module 220also includes a transaction intake module 264, an inventory coordinationmodule 226, a synchronization server module 256, a financial executionmodule 224, an authentication module 246, a location services module244, a business intelligence analytics module 228, and an advertisingmodule 222. In some embodiments, integrated wireless commerce managementmodule 220 also interacts with a secure credential vault 258.

In some embodiments, a transaction intake module 264 includes one ormore receiving modules for receiving over a wireless data communicationchannel a tokenized first item of financial transaction information(e.g., a transaction ticket 210) from a customer mobile devicepresenting a customer-facing interface, and receiving a second item offinancial transaction information from a merchant-facing point-of-saleinterface connected to the mobile device through the wireless datacommunication channel.

In some embodiments, a financial execution module 224 includes a pointof sale server for rendering in a common internal format the first itemof financial transaction information from the customer-facing interface,and rendering in the common internal format the second item of financialtransaction information from the merchant-facing point-of-saleinterface. In some embodiments, the financial execution module 224further includes a payment processing module for rendering in a secondformat the first item of financial transaction information for paymentprocessing by a first external financial party.

In some embodiments, a token resolution module 234 converts thetokenized first item of financial transaction information to anaccount-specific item of financial transaction information using anaccount identifier associated with the tokenized first item in aregistry stored in a secured account data vault, such as securedcredential vault 258.

In some embodiments, financial execution module 224 performs renderingin a third format the second item of financial transaction informationfor payment processing by a second external financial party, andtransmitting in the second format the first item of financialtransaction information for payment processing by the first externalfinancial party. In some embodiments, the second format includes thefinancial transaction information using the account identifierassociated with the tokenized first item in a registry stored in asecured account data vault, such as secured credential vault 258. Insome embodiments, financial execution module 224 performs transmittingin the third format the second item of financial transaction informationas a transaction execution order 270 for payment processing by thesecond external financial party. In some embodiments, the transmittingin the second format the first item of financial transaction informationfor payment processing by the first external financial party, furtherincludes transmitting in the second format the first item of financialtransaction information for payment processing by the first externalfinancial party, wherein the second format includes the financialtransaction information using the account identifier associated with thetokenized first item in a registry stored in the secured account datavault without transmitting the financial transaction information usingthe account identifier associated with the tokenized first item in theregistry stored in the secured account data vault to the merchant-facingpoint-of-sale interface.

Some embodiments include an authentication module for recognizing, usinga location services module 244, a customer mobile device located in anarea defined within a geofence, identifying a customer associated withthe customer mobile device based at least in part on a presence of anapplication executing on the customer mobile device, and issuing asession token to the application on the customer mobile device.

In some embodiments, the transaction intake module 264 receiving over awireless data communication channel a tokenized first item of financialtransaction information from a customer mobile device presenting acustomer-facing interface further includes receiving over a Bluetoothlow energy radio communication channel a tokenized first item offinancial transaction information from a customer mobile devicepresenting a customer-facing interface.

In some embodiments, the transaction intake module 264 receiving asecond item of financial transaction information from a merchant-facingpoint-of-sale interface connected to the mobile device through thewireless data communication channel further includes receiving over abroadband wireless network a second item of financial transactioninformation from a merchant-facing point-of-sale interface connected tothe mobile device through the wireless data communication channel.

In some embodiments, the transaction intake module 264 the one or morereceiving modules include a single stack application program interfaceresiding on one of the one or more servers. In some embodiments, thetransaction execution module is further configured for receiving on theone or more servers a transaction authorization confirmation from thefirst external financial party, and the point of sale server is furtherconfigured for transmitting to the customer-facing interface anindication of the transaction authorization confirmation.

In some embodiments, the payment processing module includes a paymentprocessing gateway for communicating with servers of external financialprocessors using encrypted links over a network.

In some embodiments, integrated wireless commerce management module 220implements or supports a system for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms. In some embodiments,integrated wireless commerce management module 220 includes one or morecomputers configured to implement by executing instructions on one ormore processors a platform-agnostic transaction-related communicationsystem. In some embodiments, integrated wireless commerce managementmodule 220 includes software for execution on one or more computersconfigured to implement by executing instructions on one or moreprocessors a platform-agnostic transaction-related communication system.In some embodiments, the transaction-related communication systemincludes one or more receiving modules, such as transaction intakemodule 224, for receiving a first item of financial transactioninformation from a customer-facing interface, such as a user interface222, which may be implemented on integrated wireless commerce managementmodule 220 or in a separate system, and receiving a second item offinancial transaction information from a merchant-facing point-of-saleinterface.

In some embodiments, the transaction-related communication systemincludes a point of sale server, for example as a component of financialexecution module 224, for rendering in a common internal format (forexample, for storage on storage medium 240 as unified formattransactions 260) the first item of financial transaction informationfrom the customer-facing interface of user interface 222, and renderingin the common internal format (for example, for storage on storagemedium 240 as unified format transactions 260) the second item offinancial transaction information from the merchant-facing point-of-saleinterface. In some embodiments, the transaction-related communicationsystem includes a payment processing module, for example as a componentof financial execution module 224, for rendering in a second format (forexample, as transaction execution orders 250) the first item offinancial transaction information for payment processing by a firstexternal financial party, and rendering in a third format (for example,as transaction execution orders 250) the first item of financialtransaction information for payment processing by a second externalfinancial party.

In some embodiments, the transaction-related communication systemincludes a transaction execution module, for example as a component offinancial execution module 224, for transmitting in the second formatthe first item of financial transaction information for paymentprocessing by the first external financial party, and transmitting inthe third format the second item of financial transaction informationfor payment processing by the second external financial party.

In some embodiments, the system uses integrated wireless commercemanagement module 220 for providing payment processing services from aplurality of disparate payment processors to a plurality of disparatetransaction intake platforms. In some embodiments, the common internalformat is a common intake transaction ticket format, which may be usedin unified format transactions 260. In some embodiments, the one or morereceiving modules, such as transaction intake module 224, include asingle stack application program interface residing on one of the one ormore servers that host or include integrated wireless commercemanagement module 220. In some embodiments, the receiving the first itemof financial transaction information, such as transaction tickets 210,from a customer-facing interface further includes receiving in thecommon intake transaction ticket format over the network from a mobilecomputing device the first item of financial transaction informationfrom the customer-facing interface, such as a user interface 222implemented on a system remote from integrated wireless commercemanagement module 220. In some embodiments, the receiving the seconditem of financial transaction information, such as transaction tickets210, from the merchant-facing point-of-sale interface further includesreceiving over the network in the common intake transaction ticketformat the second item of financial transaction information from themerchant-facing point-of-sale interface.

In some embodiments, the common internal format is a common intaketransaction ticket format for use in transaction tickets 210. In someembodiments, the system further includes a first translation module on amobile computing device, such as a user interface 222 implemented on asystem remote from integrated wireless commerce management module 220,for receiving from a customer facing application including thecustomer-facing interface on the mobile computing device the first itemof financial transaction information, and translating to a common intaketransaction ticket format the first item of financial transactioninformation. In some embodiments, the system further includes a secondtranslation module on a merchant-facing point of sale device forreceiving from a merchant facing application including themerchant-facing point-of-sale interface on a merchant point of saledevice the second item of financial transaction information, andtranslating to the common intake transaction ticket format the seconditem of financial transaction information.

In some embodiments, the one or more receiving modules, such astransaction intake module 224, include a single stack applicationprogram interface residing on one of the one or more servers that hostor include integrated wireless commerce management module 220. In someembodiments, a server communicates remotely with the mobile computingdevice over a wireless network. In some embodiments, the servercommunicates remotely with the merchant-facing point of sale device overa second network. In some embodiments, the receiving the first item offinancial transaction information from the customer-facing interfacefurther includes receiving in the common intake transaction ticketformat at the single stack application interface from the mobilecomputing device the first item of financial transaction informationfrom the customer-facing interface. In some embodiments, the receivingthe second item of financial transaction information from themerchant-facing point-of-sale interface further includes receiving inthe common intake transaction ticket format at the single stackapplication interface the second item of financial transactioninformation from the merchant-facing point-of-sale interface.

In some embodiments, the transaction execution module, such as financialexecution module 224, is further configured for receiving on the one ormore servers a transaction authorization confirmation from the firstexternal financial party, and the point of sale server is furtherconfigured for transmitting to the customer-facing interface anindication of the transaction authorization confirmation. In someembodiments, the payment processing module, such as financial executionmodule 224, includes a payment processing gateway for communicating withservers of external financial processors using encrypted links over anetwork.

In some embodiments, the system for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms further includes a businessintelligence analytics module 228 for providing business intelligencebased at least in part on the first item of financial transactioninformation. In some embodiments, such business intelligence includesrisk assessment for use in deciding whether to authorize or denyauthorization for a transaction.

In some embodiments, the system for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms further includes an inventorycoordination module 226 for providing transaction fulfillmentinformation based at least in part on the first item of financialtransaction information. In some embodiments, the inventory coordinationmodule 226 enables the integrated wireless commerce module 220 tomonitor consolidated stock levels and determine when to re-order,without relying on additional systems or manual reporting, therebyenabling merchants to provide a consistent, seamless experience forconsumers across all channels, including offering returns through anychannel no matter where the purchase originated.

In some embodiments, the financial execution module 224 supportsreconciling accounts for every channel, such that merchants mayconsolidate accounts with payment processors and accounting systems,without manual posting of entries.

Some embodiments of integrated wireless commerce management module 220support a merchant that operates a physical store, operates an onlinestore, accepts payments on a mobile device, or any combination of thosechannels. Some embodiments of integrated wireless commerce managementmodule 220 present a single merchant account to reduce reconciliationand accounting headaches and to provide one version of the data throughconsolidated reports across all channels and touchpoints. Someembodiments of integrated wireless commerce management module 220 canalso handle the issues of managing inventory across mobile ande-commerce touchpoints, as well as in the store, providing a single viewof the merchandise that's available to sell, and helping businessesbalance between inventory and demand.

Some embodiments of integrated wireless commerce management module 220support a cloud-based point-of-sale, mobile and eCommerce framework thatintegrates payments with inventory management.

Some embodiments of integrated wireless commerce management module 220real-time, in-app inventory tracking, management and replenishmentdirectly from a mobile application. Some embodiments of integratedwireless commerce management module 220 provide import and exportcapabilities that allow merchants to easily transfer and integrateinventory data into other systems. Some embodiments of integratedwireless commerce management module 220 provide Integration with thirdparty eCommerce platforms—sales and inventory data by location providesmerchants more valuable insights into their business. Some embodimentsof integrated wireless commerce management module 220 provide theability to set replenishment thresholds and alerts and transferinventory between locations and channels. Some embodiments of integratedwireless commerce management module 220 adjust inventory for sales andreturns in real-time and can also work with a merchant's existinginventory platform, by allowing merchants to integrate in to someembodiments of integrated wireless commerce management module 220 usingapplication program interfaces.

Some embodiments of integrated wireless commerce management module 220can also solve the problems of the friction points mentioned above byeliminating disparate payment processors and processing rates, furthersimplifying reconciliation across all of a merchant's selling channels.In moving to a single payments provider under some embodiments,merchants can also take advantage of volume pricing, and get the bestpossible rates for each channel.

Some embodiments of integrated wireless commerce management module 220provide business insights, such merchants can leverage data to optimizesales, for example such as how much floor space to allocate to specificproducts, what items and locations provide the most revenue and profitand what products to feature. Merchants also have the ability to storecustomer history, past purchases and other customer-specific data tohelp them become more customer-centric. These systems open the door tointegrated loyalty programs and other customer relationship managementtools to help merchants know who their best customers are and how tobest reach them how, when and where the customer wants to shop.

Some embodiments of integrated wireless commerce management module 220also allow developers to integrate payments, inventory and businessinsights into their platforms through the only single stack ofapplication program interfaces for card present and card not presenttransactions.

In some embodiments, the synchronization server module 226 implements asynchronization server protocol that synchronizes data between a server,such as one of the one or more servers that host or include integratedwireless commerce management module 220, and clients, such as orderingcustomer client 110 or merchant client 120 of FIG. 1 , providing objectsfrom database 102 of FIG. 1 from storage medium 240 that the clientshave not received or that have been updated since client receipt.

In some embodiments, data synchronization from synchronization servermodule 226 allows clients to execute transactions or parts oftransactions offline without querying one of the one or more serversthat host or include integrated wireless commerce management module 220,instead using local copies of objects from database 102 of FIG. 1 . Insome embodiments, database objects stored in storage medium 240 includeserial numbers, and based on the serial number, and the fact thatclients store a serial number (called an update ID) for their mostrecent transaction update, clients may send to one of the one or moreservers that host or include integrated wireless commerce managementmodule 220 a database-wide pointer indicating the client's last receivedobject (inserted or updated) to request from synchronization servermodule 226. In some embodiments, serial numbers for objects stored instorage medium 240 are assigned at object creation and new serialnumbers are assigned at object update.

In some embodiments, synchronization server module receives a serialnumber and a list of query objects or object types of interest to theclient and replies in the background of transaction flow with an updateof all data (both new and updated) with serial numbers assigned afterthe pointer. In some embodiments, this update allows for off-peakupdates of the database outside of time-critical traffic flow. Theclient then assimilates the reply objects into a local (sometimespartial) mirror copy of the database, as well as saving the pointer ofthe last updated object for use in the next query. When the client isupdating certain objects for its own transaction, synchronization servermodule 226 also provides the updated state of the objects created orupdated by the client and sends the update ID and modified and newobjects resulting from the transaction, as well as any that may havebeen modified by another client.

Some embodiments include a system (such as integrated wireless commercemanagement module 220) for providing inventory management services froma plurality of disparate inventory resources for transactions receivedfrom a plurality of disparate transaction intake platforms. In someembodiments, one or more computers configured to implement an integratedwireless commerce management module 220 executes instructions on one ormore processors for a platform-agnostic transaction-relatedcommunication system. In some embodiments, the transaction-relatedcommunication system includes one or more receiving modules, such astransaction intake module 224, configured for receiving a first item ofinventory transaction information, such as transaction tickets 210 froma customer-facing interface, for example, in some embodiments, through auser interface 222 and receiving a second item of inventory transactioninformation from, such as transaction tickets 210 a merchant-facingpoint-of-sale interface. In some embodiments, the transaction-relatedcommunication system includes an inventory coordination module 226configured for rendering in a common internal format the first item ofinventory transaction information, for example, as unified formattransactions 260 from the customer-facing interface, and rendering inthe common internal format the second item of inventory transactioninformation, for example, as unified format transactions 260 from themerchant-facing point-of-sale interface. In some embodiments, thetransaction-related communication system includes an inventorycoordination module 226 configured for transmitting the second item ofinventory transaction information, for example, as unified inventorydata 220 or transaction execution orders for inventory transactionexecution by the second inventory resource, and transmitting the firstitem of inventory transaction information for inventory transactionexecution by a first inventory resource.

In some embodiments, the transaction-related communication systemincludes a synchronization server module 226 configured for providingbackground updates of transactions including in some embodiments unifiedinventory data 220 and/or unified format transactions 260 to thecustomer facing interface and the merchant-facing point of saleinterface. In some embodiments, the receiving the first item ofinventory transaction information (for example, as user input 212) fromthe customer-facing interface further includes receiving in the commonintake transaction ticket format as transaction tickets 210 over thenetwork from a mobile computing device an order for an item as the firstitem of inventory transaction information from the customer-facinginterface (e.g., user interface 222). In some embodiments, the receivingthe second item of inventory transaction information from themerchant-facing point-of-sale interface further includes receiving overthe network in the common intake transaction ticket format (for example,as a transaction ticket 210) a return of the item as the second item ofinventory transaction information from the merchant-facing point-of-saleinterface. In some embodiments, the inventory coordination module 226 isfurther configured for updating a unified inventory database in storagemedium 240 to reflect fulfillment of the order for the item, and theinventory coordination module is further configured for updating aunified inventory database to reflect fulfillment of the return of theitem.

In some embodiments, the receiving the first item of inventorytransaction information (for example, as a transaction ticket 210) fromthe customer-facing interface further includes receiving in the commonintake transaction ticket format over the network from a mobilecomputing device an order for an item as the first item of inventorytransaction information from the customer-facing interface (e.g., userinterface 222). In some embodiments, the receiving the second item ofinventory transaction information (for example, as a transaction ticket210) from the merchant-facing point-of-sale interface further includesreceiving over the network in the common intake transaction ticketformat a return of the item as the second item of inventory transactioninformation from the merchant-facing point-of-sale interface. In someembodiments, the inventory coordination module 226 is further configuredfor querying a unified inventory database, for example, in storagemedium 240, to ascertain whether fulfillment of the order for the itemis possible, and the inventory coordination module 226 is furtherconfigured for updating a unified inventory database to reflectfulfillment of the return of the item.

In some embodiments, the common internal format is a common intaketransaction ticket format for use in unified format transactions 260and/or unified inventory data 220, and the one or more receivingmodules, such as transaction intake module 224, include a single stackapplication program interface residing on one of the one or more serversthat house integrated wireless commerce management module 220.

In some embodiments, the receiving the first item of inventorytransaction information (for example, as a transaction ticket 210) fromthe customer-facing interface, for example, user interface 222, furtherincludes receiving in the common intake transaction ticket format (forexample, as a transaction ticket 210) over the network from a mobilecomputing device an order for an item as the first item of inventorytransaction information from the customer-facing interface. In someembodiments, the receiving the second item of inventory transactioninformation (for example, as a transaction ticket 210) from themerchant-facing point-of-sale interface further includes receiving overthe network in the common intake transaction ticket format a return ofthe item as the second item of inventory transaction information fromthe merchant-facing point-of-sale interface. In some embodiments, theinventory coordination module 226 is further configured for updating aunified inventory database (for example, by sending unified inventorydata 220 to storage medium 240) to reflect fulfillment of the order forthe item from an inventory warehouse resource. In some embodiments, theinventory coordination module is further configured for updating aunified inventory database (for example, by sending unified inventorydata 220 to storage medium 240) to reflect fulfillment of the return ofthe item by updating an in-stock inventory count for a brick-and-mortarretail location housing the merchant-facing point-of-sale interface.

In some embodiments, the system further includes a business intelligenceanalytics module 228 configured for providing business intelligencebased at least in part on the inventory transaction information.

FIG. 2B is a flowchart of a process for a wireless data communicationinterface, according to some embodiments. A customer mobile device and aterminal of merchant-facing point-of-sale (POS) hardware initiate asession over a radio-frequency network or a radio-frequency link (block2000). The merchant-facing POS hardware generates transaction ticket(e.g., by recording items) (block 2002). The merchant-facing POShardware transmits a transaction ticket to customer mobile device forreview and approval (block 2004). The merchant-facing POS hardwarecloses the ticket (block 2006). The merchant-facing POS hardwarerequests approval/authentication and payment method instruction fromcustomer mobile device (block 2008). The customer-facing mobile devicesends approval/authentication and payment method instruction (block2010). The merchant-facing POS transmit transaction ticket to POSserver, including merchant credentials and payment data, triggering acomplementary process described at step 800 (block 2012). Confirmationis received, resulting from a process starting at block 814 of FIG. 8 ,which is described below (block 2014). The confirmation is displayed(block 2016).

FIG. 2C is a flowchart of a process for a wireless data communicationinterface, according to some embodiments. A session is initiated (block2100). A transaction ticket is generated (block 2102). The transactionticket is transmitted for review and approval (block 2104). The ticketis closed (block 2106). Approval and authentication of the ticket with atokenized payment instruction are requested (block 2108). Approval andauthentication are of the ticket are sent with a tokenized paymentinstruction (block 2110). The transaction ticket is transmitted to a POSserver, including merchant credentials and tokenized payment data,triggering a process described below with respect to block 800 of FIG. 8(block 2112). Confirmation is received, resulting from a processstarting at block 804 of FIG. 8 , which is described below (block 2114).The confirmation is displayed (block 2116).

FIG. 2D is a flowchart of a process on a customer mobile device for awireless data communication interface, according to some embodiments. Acustomer mobile device and merchant-facing POS hardware initiate session(block 2210). The customer mobile device receives or generatestransaction ticket (block 2212). The customer mobile device transmits(an updated) transaction ticket to merchant-facing POS hardware (block2214). The customer mobile device sends approval/authentication andtokenized payment method instruction (block 2216). Tokenized paymentconfirmation (block 2218). Tokenized payment confirmation is displayed(block 2220).

FIG. 2E is a flowchart of a process on a unit of merchant-facing POShardware for a wireless data communication interface, according to someembodiments. Merchant-facing point-of-sale hardware initiates a session(block 2300). The merchant-facing POS hardware generates transactionticket (e.g., by recording items) (block 2302). The merchant-facing POShardware transmits transaction ticket for review and approval (block2304). The merchant-facing POS hardware closes the ticket (block 2306).The merchant-facing POS hardware requests approval/authentication andtokenized payment method instruction (block 2308). The merchant-facingPOS hardware receives approval/authentication and tokenized paymentmethod instruction (block 2310). The merchant-facing POS hardwaretransmits transaction ticket to POS server, including merchantcredentials and tokenized payment data (as described below with respectto block 800 in FIG. 8 ) (block 2312). The merchant-facing POS hardwarereceives confirmation (as described below with respect to block 814 inFIG. 8 ) (block 2314). The merchant-facing POS hardware displaysconfirmation (block 2316).

FIG. 2F is a flowchart of a process on a unit of merchant-facing POShardware for a wireless data communication interface, according to someembodiments. The merchant-facing POS hardware recognizes customer devicein geofence (block 2400). Identity of customer is verified on basis ofapp on customer mobile device (block 2402). The merchant-facing POShardware issues session token to app on customer mobile device (block2404).

FIG. 2G is a flowchart of a process on a unit of merchant-facing POShardware for a wireless data communication interface, according to someembodiments. The merchant-facing POS hardware recognizes the customerdevice in the geofence (block 2500). The identity of the customer isverified on basis of app on customer mobile device (block 2502). Themerchant-facing POS hardware issues a session token to the applicationon the customer mobile device (block 2504). The merchant-facing POShardware creates the ticket with scanned product (block 2506). Theticket is displayed on the customer mobile device (block 2508). Thecustomer mobile device transmits payment approval/securityauthentication and tokenized payment method instruction (block 2510).The merchant-facing POS hardware receives the approval/authenticationand tokenized payment method instruction (block 2512). Themerchant-facing POS hardware transmits transaction ticket to POS server,including merchant credentials and tokenized payment data from tokenvault, as is described below with respect to FIG. 8 at block 800 (block2514). The merchant-facing POS hardware receives confirmation, resultingfrom a process described below with respect to block 814 in FIG. 8(block 2516). The merchant-facing POS hardware displays confirmation(block 2518).

FIG. 3 depicts a module that may implement unified inventory andfinancial transaction management, according to some embodiments. Anelectronic commerce management module 320 receives as input transactionexecution confirmations 370 transaction tickets 310 and user input 312(for example, in some embodiments, through a user interface 322) andstores transaction execution orders 350, unified inventory data 330, andunified format transactions 360 in a storage medium 340. Electroniccommerce management module 320 is one embodiment of integrated wirelesscommerce module 104 of FIG. 1 , which is discussed above.

In some embodiments, electronic commerce management module 320 includesa transaction intake module 324, an inventory coordination module 326, asynchronization server module 336, a financial execution module 334, abusiness intelligence analytics module 328, and an advertising module332.

In some embodiments, electronic commerce management module 320implements or supports a system for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms. In some embodiments,electronic commerce management module 320 includes one or more computersconfigured to implement by executing instructions on one or moreprocessors a platform-agnostic transaction-related communication system.In some embodiments, electronic commerce management module 320 includessoftware for execution on one or more computers configured to implementby executing instructions on one or more processors a platform-agnostictransaction-related communication system. In some embodiments, thetransaction-related communication system includes one or more receivingmodules, such as transaction intake module 324, for receiving a firstitem of financial transaction information from a customer-facinginterface, such as a user interface 322, which may be implemented onelectronic commerce management module 320 or in a separate system, andreceiving a second item of financial transaction information from amerchant-facing point-of-sale interface.

In some embodiments, the transaction-related communication systemincludes a point of sale server, for example as a component of financialexecution module 334, for rendering in a common internal format (forexample, for storage on storage medium 340 as unified formattransactions 360) the first item of financial transaction informationfrom the customer-facing interface of user interface 322, and renderingin the common internal format (for example, for storage on storagemedium 340 as unified format transactions 360) the second item offinancial transaction information from the merchant-facing point-of-saleinterface. In some embodiments, the transaction-related communicationsystem includes a payment processing module, for example as a componentof financial execution module 334, for rendering in a second format (forexample, as transaction execution orders 350) the first item offinancial transaction information for payment processing by a firstexternal financial party, and rendering in a third format (for example,as transaction execution orders 350) the first item of financialtransaction information for payment processing by a second externalfinancial party.

In some embodiments, the transaction-related communication systemincludes a transaction execution module, for example as a component offinancial execution module 334, for transmitting in the second formatthe first item of financial transaction information for paymentprocessing by the first external financial party, and transmitting inthe third format the second item of financial transaction informationfor payment processing by the second external financial party.

In some embodiments, the system uses electronic commerce managementmodule 320 for providing payment processing services from a plurality ofdisparate payment processors to a plurality of disparate transactionintake platforms. In some embodiments, the common internal format is acommon intake transaction ticket format, which may be used in unifiedformat transactions 360. In some embodiments, the one or more receivingmodules, such as transaction intake module 324, include a single stackapplication program interface residing on one of the one or more serversthat host or include electronic commerce management module 320. In someembodiments, the receiving the first item of financial transactioninformation, such as transaction tickets 310, from a customer-facinginterface further includes receiving in the common intake transactionticket format over the network from a mobile computing device the firstitem of financial transaction information from the customer-facinginterface, such as a user interface 322 implemented on a system remotefrom electronic commerce management module 320. In some embodiments, thereceiving the second item of financial transaction information, such astransaction tickets 310, from the merchant-facing point-of-saleinterface further includes receiving over the network in the commonintake transaction ticket format the second item of financialtransaction information from the merchant-facing point-of-saleinterface.

In some embodiments, the common internal format is a common intaketransaction ticket format for use in transaction tickets 310. In someembodiments, the system further includes a first translation module on amobile computing device, such as a user interface 322 implemented on asystem remote from electronic commerce management module 320, forreceiving from a customer facing application including thecustomer-facing interface on the mobile computing device the first itemof financial transaction information, and translating to a common intaketransaction ticket format the first item of financial transactioninformation. In some embodiments, the system further includes a secondtranslation module on a merchant-facing point of sale device forreceiving from a merchant facing application including themerchant-facing point-of-sale interface on a merchant point of saledevice the second item of financial transaction information, andtranslating to the common intake transaction ticket format the seconditem of financial transaction information.

In some embodiments, the one or more receiving modules, such astransaction intake module 324, include a single stack applicationprogram interface residing on one of the one or more servers that hostor include electronic commerce management module 320. In someembodiments, a server communicates remotely with the mobile computingdevice over a wireless network. In some embodiments, the servercommunicates remotely with the merchant-facing point of sale device overa second network. In some embodiments, the receiving the first item offinancial transaction information from the customer-facing interfacefurther includes receiving in the common intake transaction ticketformat at the single stack application interface from the mobilecomputing device the first item of financial transaction informationfrom the customer-facing interface. In some embodiments, the receivingthe second item of financial transaction information from themerchant-facing point-of-sale interface further includes receiving inthe common intake transaction ticket format at the single stackapplication interface the second item of financial transactioninformation from the merchant-facing point-of-sale interface.

In some embodiments, the transaction execution module, such as financialexecution module 334, is further configured for receiving on the one ormore servers a transaction authorization confirmation from the firstexternal financial party, and the point of sale server is furtherconfigured for transmitting to the customer-facing interface anindication of the transaction authorization confirmation. In someembodiments, the payment processing module, such as financial executionmodule 334, includes a payment processing gateway for communicating withservers of external financial processors using encrypted links over anetwork.

In some embodiments, the system for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms further includes a businessintelligence analytics module 328 for providing business intelligencebased at least in part on the first item of financial transactioninformation. In some embodiments, such business intelligence includesrisk assessment for use in deciding whether to authorize or denyauthorization for a transaction.

In some embodiments, the system for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms further includes an inventorycoordination module 326 for providing transaction fulfillmentinformation based at least in part on the first item of financialtransaction information. In some embodiments, the inventory coordinationmodule 326 enables the integrated electronic commerce module 320 tomonitor consolidated stock levels and determine when to re-order,without relying on additional systems or manual reporting, therebyenabling merchants to provide a consistent, seamless experience forconsumers across all channels, including offering returns through anychannel no matter where the purchase originated.

In some embodiments, the financial execution module 334 supportsreconciling accounts for every channel, such that merchants mayconsolidate accounts with payment processors and accounting systems,without manual posting of entries.

Some embodiments of electronic commerce management module 320 support amerchant that operates a physical store, operates an online store, andaccepts payments on a mobile device, or any combination of thosechannels. Some embodiments of electronic commerce management module 320present a single merchant account to reduce reconciliation andaccounting headaches and to provide one version of the data throughconsolidated reports across all channels and touchpoints. Someembodiments of electronic commerce management module 320 can also handlethe issues of managing inventory across mobile and e-commercetouchpoints, as well as in the store, providing a single view of themerchandise that's available to sell, and helping businesses balancebetween inventory and demand.

Some embodiments of electronic commerce management module 320 support acloud-based point-of-sale, mobile and eCommerce framework thatintegrates payments with inventory management.

Some embodiments of electronic commerce management module 320 real-time,in-app inventory tracking, management and replenishment directly from amobile application. Some embodiments of electronic commerce managementmodule 320 provide import and export capabilities that allow merchantsto easily transfer and integrate inventory data into other systems. Someembodiments of electronic commerce management module 320 provideIntegration with third party eCommerce platforms—sales and inventorydata by location provides merchants more valuable insights into theirbusiness. Some embodiments of electronic commerce management module 320provide the ability to set replenishment thresholds and alerts andtransfer inventory between locations and channels. Some embodiments ofelectronic commerce management module 320 adjust inventory for sales andreturns in real-time and can also work with a merchant's existinginventory platform, by allowing merchants to integrate in to someembodiments of electronic commerce management module 320 usingapplication program interfaces.

Some embodiments of electronic commerce management module 320 can alsosolve the problems of the friction points mentioned above by eliminatingdisparate payment processors and processing rates, further simplifyingreconciliation across all of a merchant's selling channels. In moving toa single payments provider under some embodiments, merchants can alsotake advantage of volume pricing, and get the best possible rates foreach channel.

Some embodiments of electronic commerce management module 320 providebusiness insights, such merchants can leverage data to optimize sales,for example such as how much floor space to allocate to specificproducts, what items and locations provide the most revenue and profitand what products to feature. Merchants also have the ability to storecustomer history, past purchases and other customer-specific data tohelp them become more customer-centric. These systems open the door tointegrated loyalty programs and other customer relationship managementtools to help merchants know who their best customers are and how tobest reach them how, when and where the customer wants to shop.

Some embodiments of electronic commerce management module 320 also allowdevelopers to integrate payments, inventory and business insights intotheir platforms through the only single stack of application programinterfaces for card present and card not present transactions.

In some embodiments, the synchronization server module 336 implements asynchronization server protocol that synchronizes data between a server,such as one of the one or more servers that host or include electroniccommerce management module 320, and clients, such as ordering customerclient 110 or merchant client 120 of FIG. 1 , providing objects fromdatabase 102 of FIG. 1 from storage medium 340 that the clients have notreceived or that have been updated since client receipt.

In some embodiments, data synchronization from synchronization servermodule 336 allows clients to execute transactions or parts oftransactions offline without querying one of the one or more serversthat host or include electronic commerce management module 320, insteadusing local copies of objects from database 102 of FIG. 1 . In someembodiments, database objects stored in storage medium 340 includeserial numbers, and based on the serial number, and the fact thatclients store a serial number (called an update ID) for their mostrecent transaction update, clients may send to one of the one or moreservers that host or include electronic commerce management module 320 adatabase-wide pointer indicating the client's last received object(inserted or updated) to request from synchronization server module 336.In some embodiments, serial numbers for objects stored in storage medium340 are assigned at object creation and new serial numbers are assignedat object update.

In some embodiments, synchronization server module receives a serialnumber and a list of query objects or object types of interest to theclient and replies in the background of transaction flow with an updateof all data (both new and updated) with serial numbers assigned afterthe pointer. In some embodiments, this update allows for off-peakupdates of the database outside of time-critical traffic flow. Theclient then assimilates the reply objects into a local (sometimespartial) mirror copy of the database, as well as saving the pointer ofthe last updated object for use in the next query. When the client isupdating certain objects for its own transaction, synchronization servermodule 336 also provides the updated state of the objects created orupdated by the client and sends the update ID and modified and newobjects resulting from the transaction, as well as any that may havebeen modified by another client.

Some embodiments include a system (such as electronic commercemanagement module 320) for providing inventory management services froma plurality of disparate inventory resources for transactions receivedfrom a plurality of disparate transaction intake platforms. In someembodiments, one or more computers configured to implement an electroniccommerce management module 320 executes instructions on one or moreprocessors for a platform-agnostic transaction-related communicationsystem. In some embodiments, the transaction-related communicationsystem includes one or more receiving modules, such as transactionintake module 324, configured for receiving a first item of inventorytransaction information, such as transaction tickets 310 from acustomer-facing interface, for example, in some embodiments, through auser interface 322 and receiving a second item of inventory transactioninformation from, such as transaction tickets 310 a merchant-facingpoint-of-sale interface. In some embodiments, the transaction-relatedcommunication system includes an inventory coordination module 326configured for rendering in a common internal format the first item ofinventory transaction information, for example, as unified formattransactions 360 from the customer-facing interface, and rendering inthe common internal format the second item of inventory transactioninformation, for example, as unified format transactions 360 from themerchant-facing point-of-sale interface. In some embodiments, thetransaction-related communication system includes an inventorycoordination module 326 configured for transmitting the second item ofinventory transaction information, for example, as unified inventorydata 330 or transaction execution orders for inventory transactionexecution by the second inventory resource, and transmitting the firstitem of inventory transaction information for inventory transactionexecution by a first inventory resource.

In some embodiments, the transaction-related communication systemincludes a synchronization server module 336 configured for providingbackground updates of transactions including in some embodiments unifiedinventory data 330 and/or unified format transactions 360 to thecustomer facing interface and the merchant-facing point of saleinterface. In some embodiments, the receiving the first item ofinventory transaction information (for example, as user input 312) fromthe customer-facing interface further includes receiving in the commonintake transaction ticket format as transaction tickets 310 over thenetwork from a mobile computing device an order for an item as the firstitem of inventory transaction information from the customer-facinginterface (e.g., user interface 322). In some embodiments, the receivingthe second item of inventory transaction information from themerchant-facing point-of-sale interface further includes receiving overthe network in the common intake transaction ticket format (for example,as a transaction ticket 310) a return of the item as the second item ofinventory transaction information from the merchant-facing point-of-saleinterface. In some embodiments, the inventory coordination module 326 isfurther configured for updating a unified inventory database in storagemedium 340 to reflect fulfillment of the order for the item, and theinventory coordination module is further configured for updating aunified inventory database to reflect fulfillment of the return of theitem.

In some embodiments, the receiving the first item of inventorytransaction information (for example, as a transaction ticket 310) fromthe customer-facing interface further includes receiving in the commonintake transaction ticket format over the network from a mobilecomputing device an order for an item as the first item of inventorytransaction information from the customer-facing interface (e.g., userinterface 322). In some embodiments, the receiving the second item ofinventory transaction information (for example, as a transaction ticket310) from the merchant-facing point-of-sale interface further includesreceiving over the network in the common intake transaction ticketformat a return of the item as the second item of inventory transactioninformation from the merchant-facing point-of-sale interface. In someembodiments, the inventory coordination module 326 is further configuredfor querying a unified inventory database, for example, in storagemedium 340, to ascertain whether fulfillment of the order for the itemis possible, and the inventory coordination module 326 is furtherconfigured for updating a unified inventory database to reflectfulfillment of the return of the item.

In some embodiments, the common internal format is a common intaketransaction ticket format for use in unified format transactions 360and/or unified inventory data 330, and the one or more receivingmodules, such as transaction intake module 324, include a single stackapplication program interface residing on one of the one or more serversthat house electronic commerce management module 320.

In some embodiments, the receiving the first item of inventorytransaction information (for example, as a transaction ticket 310) fromthe customer-facing interface, for example, user interface 322, furtherincludes receiving in the common intake transaction ticket format (forexample, as a transaction ticket 310) over the network from a mobilecomputing device an order for an item as the first item of inventorytransaction information from the customer-facing interface. In someembodiments, the receiving the second item of inventory transactioninformation (for example, as a transaction ticket 310) from themerchant-facing point-of-sale interface further includes receiving overthe network in the common intake transaction ticket format a return ofthe item as the second item of inventory transaction information fromthe merchant-facing point-of-sale interface. In some embodiments, theinventory coordination module 326 is further configured for updating aunified inventory database (for example, by sending unified inventorydata 330 to storage medium 340) to reflect fulfillment of the order forthe item from an inventory warehouse resource. In some embodiments, theinventory coordination module is further configured for updating aunified inventory database (for example, by sending unified inventorydata 330 to storage medium 340) to reflect fulfillment of the return ofthe item by updating an in-stock inventory count for a brick-and-mortarretail location housing the merchant-facing point-of-sale interface.

In some embodiments, the system further includes a business intelligenceanalytics module 328 configured for providing business intelligencebased at least in part on the inventory transaction information.

FIG. 4 illustrates a module that may implement unified inventory andfinancial transaction management, according to some embodiments. Anelectronic commerce management module 420 receives as input transactionconfirmations 470, transaction tickets 410 and user input 412 (forexample, in some embodiments, through a user interface 422) and storestransaction execution orders 450, unified inventory data 430, andunified format transactions 460 in a storage medium 440. Electroniccommerce management module 420 is one embodiment of integratedelectronic commerce module 204 of FIG. 2 , which is discussed above.

In some embodiments, electronic commerce management module 420 includesa transaction intake module such as a gateway application programinterface 424, an inventory coordination module 426, a synchronizationserver module 436, a financial execution module such as a paymentprocessing gateway 434, a business intelligence analytics module 428,and an advertising module 432.

In some embodiments, electronic commerce management module 420implements or supports a system for providing payment processingservices from a plurality of disparate payment processors to a pluralityof disparate transaction intake platforms. In some embodiments,electronic commerce management module 420 includes one or more computersconfigured to implement by executing instructions on one or moreprocessors a platform-agnostic transaction-related communication system.In some embodiments, electronic commerce management module 420 includessoftware for execution on one or more computers configured to implementby executing instructions on one or more processors a platform-agnostictransaction-related communication system. In some embodiments, thetransaction-related communication system includes one or more receivingmodules, such as gateway application program interface 424, forreceiving a first item of financial transaction information from acustomer-facing interface, such as a user interface 422, which may beimplemented on electronic commerce management module 420 or in aseparate system, and receiving a second item of financial transactioninformation from a merchant-facing point-of-sale interface.

In some embodiments, the transaction-related communication systemincludes a point of sale server 438, for example as a complement ofpayment processing gateway 434, for rendering in a common internalformat (for example, for storage on storage medium 440 as unified formattransactions 460) the first item of financial transaction informationfrom the customer-facing interface of user interface 422, and renderingin the common internal format (for example, for storage on storagemedium 440 as unified format transactions 460) the second item offinancial transaction information from the merchant-facing point-of-saleinterface. In some embodiments, the transaction-related communicationsystem includes a payment processing module, for example as a componentof payment processing gateway 434, for rendering in a second format (forexample, as transaction execution orders 450) the first item offinancial transaction information for payment processing by a firstexternal financial party, and rendering in a third format (for example,as transaction execution orders 450) the first item of financialtransaction information for payment processing by a second externalfinancial party.

In some embodiments, the transaction-related communication systemincludes a transaction execution module, for example as a component ofpayment processing gateway 434, for transmitting in the second formatthe first item of financial transaction information for paymentprocessing by the first external financial party, and transmitting inthe third format the second item of financial transaction informationfor payment processing by the second external financial party. In someembodiments, the transaction execution module supports reconcilingaccounts for every channel, such that merchants may consolidate accountswith payment processors and accounting systems, without manual postingof entries.

In some embodiments, the system uses electronic commerce managementmodule 420 for providing payment processing services from a plurality ofdisparate payment processors to a plurality of disparate transactionintake platforms. In some embodiments, the common internal format is acommon intake transaction ticket format, which may be used in unifiedformat transactions 460. In some embodiments, the one or more receivingmodules, such as gateway application program interface 424, include asingle stack application program interface residing on one of the one ormore servers that host or include electronic commerce management module420. In some embodiments, the receiving the first item of financialtransaction information, such as transaction tickets 410, from acustomer-facing interface further includes receiving in the commonintake transaction ticket format over the network from a mobilecomputing device the first item of financial transaction informationfrom the customer-facing interface, such as a user interface 422implemented on a system remote from electronic commerce managementmodule 420. In some embodiments, the receiving the second item offinancial transaction information, such as transaction tickets 410, fromthe merchant-facing point-of-sale interface further includes receivingover the network in the common intake transaction ticket format thesecond item of financial transaction information from themerchant-facing point-of-sale interface.

In some embodiments, the common internal format is a common intaketransaction ticket format for use in transaction tickets 410. In someembodiments, the system further includes a first translation module on amobile computing device, such as a user interface 422 implemented on asystem remote from electronic commerce management module 420, forreceiving from a customer facing application including thecustomer-facing interface on the mobile computing device the first itemof financial transaction information, and translating to a common intaketransaction ticket format the first item of financial transactioninformation. In some embodiments, the system further includes a secondtranslation module on a merchant-facing point of sale device forreceiving from a merchant facing application including themerchant-facing point-of-sale interface on a merchant point of saledevice the second item of financial transaction information, andtranslating to the common intake transaction ticket format the seconditem of financial transaction information.

In some embodiments, the one or more receiving modules, such as gatewayapplication program interface 424, include a single stack applicationprogram interface residing on one of the one or more servers that hostor include electronic commerce management module 420. In someembodiments, a server communicates remotely with the mobile computingdevice over a wireless network. In some embodiments, the servercommunicates remotely with the merchant-facing point of sale device overa second network. In some embodiments, the receiving the first item offinancial transaction information from the customer-facing interfacefurther includes receiving in the common intake transaction ticketformat at the single stack application interface from the mobilecomputing device the first item of financial transaction informationfrom the customer-facing interface. In some embodiments, the receivingthe second item of financial transaction information from themerchant-facing point-of-sale interface further includes receiving inthe common intake transaction ticket format at the single stackapplication interface the second item of financial transactioninformation from the merchant-facing point-of-sale interface.

In some embodiments, the transaction execution module, such as paymentprocessing gateway 434, is further configured for receiving on the oneor more servers a transaction authorization confirmation from the firstexternal financial party, and the point of sale server is furtherconfigured for transmitting to the customer-facing interface anindication of the transaction authorization confirmation. In someembodiments, the payment processing module, such as payment processinggateway 434, includes a payment processing gateway for communicatingwith servers of external financial processors using encrypted links overa network.

In some embodiments, the inventory coordination module 426 enables theintegrated electronic commerce module 420 to monitor consolidated stocklevels and determine when to re-order, without relying on additionalsystems or manual reporting, thereby enabling merchants to provide aconsistent, seamless experience for consumers across all channels,including offering returns through any channel no matter where thepurchase originated.

Some embodiments of electronic commerce management module 420 support amerchant that operates a physical store, operates an online store, andaccepts payments on a mobile device, or any combination of thosechannels. Some embodiments of electronic commerce management module 420present a single merchant account to reduce reconciliation andaccounting headaches and to provide one version of the data throughconsolidated reports across all channels and touchpoints. Someembodiments of electronic commerce management module 420 can also handlethe issues of managing inventory across mobile and e-commercetouchpoints, as well as in the store, providing a single view of themerchandise that's available to sell, and helping businesses balancebetween inventory and demand.

Some embodiments of electronic commerce management module 420 support acloud-based point-of-sale, mobile and eCommerce framework thatintegrates payments with inventory management.

Some embodiments of electronic commerce management module 420 real-time,in-app inventory tracking, management and replenishment directly from amobile application. Some embodiments of electronic commerce managementmodule 420 provide import and export capabilities that allow merchantsto easily transfer and integrate inventory data into other systems. Someembodiments of electronic commerce management module 420 provideIntegration with third party eCommerce platforms—sales and inventorydata by location provides merchants more valuable insights into theirbusiness. Some embodiments of electronic commerce management module 420provide the ability to set replenishment thresholds and alerts andtransfer inventory between locations and channels. Some embodiments ofelectronic commerce management module 420 adjust inventory for sales andreturns in real-time and can also work with a merchant's existinginventory platform, by allowing merchants to integrate in to someembodiments of electronic commerce management module 420 usingapplication program interfaces.

Some embodiments of electronic commerce management module 420 can alsosolve the problems of the friction points mentioned above by eliminatingdisparate payment processors and processing rates, further simplifyingreconciliation across all of a merchant's selling channels. In moving toa single payments provider under some embodiments, merchants can alsotake advantage of volume pricing, and get the best possible rates foreach channel.

Some embodiments of electronic commerce management module 420 providebusiness insights, such merchants can leverage data to optimize sales,for example such as how much floor space to allocate to specificproducts, what items and locations provide the most revenue and profitand what products to feature. Merchants also have the ability to storecustomer history, past purchases and other customer-specific data tohelp them become more customer-centric. These systems open the door tointegrated loyalty programs and other customer relationship managementtools to help merchants know who their best customers are and how tobest reach them how, when and where the customer wants to shop.

Some embodiments of electronic commerce management module 420 also allowdevelopers to integrate payments, inventory and business insights intotheir platforms through the only single stack of application programinterfaces for card present and card not present transactions.

Some embodiments include a system (such as electronic commercemanagement module 420) for providing inventory management services froma plurality of disparate inventory resources for transactions receivedfrom a plurality of disparate transaction intake platforms. In someembodiments, one or more computers configured to implement an electroniccommerce management module 420 executes instructions on one or moreprocessors for a platform-agnostic transaction-related communicationsystem. In some embodiments, the transaction-related communicationsystem includes one or more receiving modules, such as gatewayapplication programming interface 424, configured for receiving a firstitem of inventory transaction information, such as transaction tickets410 from a customer-facing interface, for example, in some embodiments,through a user interface 422 and receiving a second item of inventorytransaction information from, such as transaction tickets 410 amerchant-facing point-of-sale interface. In some embodiments, thetransaction-related communication system includes an inventorycoordination module 426 configured for rendering in a common internalformat the first item of inventory transaction information, for example,as unified format transactions 460 from the customer-facing interface,and rendering in the common internal format the second item of inventorytransaction information, for example, as unified format transactions 460from the merchant-facing point-of-sale interface. In some embodiments,the transaction-related communication system includes an inventorycoordination module 426 configured for transmitting the second item ofinventory transaction information, for example, as unified inventorydata 430 or transaction execution orders for inventory transactionexecution by the second inventory resource, and transmitting the firstitem of inventory transaction information for inventory transactionexecution by a first inventory resource.

In some embodiments, the transaction-related communication systemincludes a synchronization server module 436 configured for providingbackground updates of transactions including in some embodiments unifiedinventory data 430 and/or unified format transactions 460 to thecustomer facing interface and the merchant-facing point of saleinterface. In some embodiments, the receiving the first item ofinventory transaction information (for example, as user input 412) fromthe customer-facing interface further includes receiving in the commonintake transaction ticket format as transaction tickets 410 over thenetwork from a mobile computing device an order for an item as the firstitem of inventory transaction information from the customer-facinginterface (e.g., user interface 422). In some embodiments, the receivingthe second item of inventory transaction information from themerchant-facing point-of-sale interface further includes receiving overthe network in the common intake transaction ticket format (for example,as a transaction ticket 410) a return of the item as the second item ofinventory transaction information from the merchant-facing point-of-saleinterface. In some embodiments, the inventory coordination module 426 isfurther configured for updating a unified inventory database in storagemedium 440 to reflect fulfillment of the order for the item, and theinventory coordination module is further configured for updating aunified inventory database to reflect fulfillment of the return of theitem.

In some embodiments, the receiving the first item of inventorytransaction information (for example, as a transaction ticket 410) fromthe customer-facing interface further includes receiving in the commonintake transaction ticket format over the network from a mobilecomputing device an order for an item as the first item of inventorytransaction information from the customer-facing interface (e.g., userinterface 322). In some embodiments, the receiving the second item ofinventory transaction information (for example, as a transaction ticket410) from the merchant-facing point-of-sale interface further includesreceiving over the network in the common intake transaction ticketformat a return of the item as the second item of inventory transactioninformation from the merchant-facing point-of-sale interface. In someembodiments, the inventory coordination module 426 is further configuredfor querying a unified inventory database, for example, in storagemedium 440, to ascertain whether fulfillment of the order for the itemis possible, and the inventory coordination module 426 is furtherconfigured for updating a unified inventory database to reflectfulfillment of the return of the item.

In some embodiments, the common internal format is a common intaketransaction ticket format for use in unified format transactions 460and/or unified inventory data 430, and the one or more receivingmodules, such as gateway application programming interface 424, includea single stack application program interface residing on one of the oneor more servers that house electronic commerce management module 320.

In some embodiments, the receiving the first item of inventorytransaction information (for example, as a transaction ticket 410) fromthe customer-facing interface, for example, user interface 422, furtherincludes receiving in the common intake transaction ticket format (forexample, as a transaction ticket 410) over the network from a mobilecomputing device an order for an item as the first item of inventorytransaction information from the customer-facing interface. In someembodiments, the receiving the second item of inventory transactioninformation (for example, as a transaction ticket 410) from themerchant-facing point-of-sale interface further includes receiving overthe network in the common intake transaction ticket format a return ofthe item as the second item of inventory transaction information fromthe merchant-facing point-of-sale interface. In some embodiments, theinventory coordination module 426 is further configured for updating aunified inventory database (for example, by sending unified inventorydata 430 to storage medium 440) to reflect fulfillment of the order forthe item from an inventory warehouse resource. In some embodiments, theinventory coordination module is further configured for updating aunified inventory database (for example, by sending unified inventorydata 430 to storage medium 440) to reflect fulfillment of the return ofthe item by updating an in-stock inventory count for a brick-and-mortarretail location housing the merchant-facing point-of-sale interface.

In some embodiments, the system further includes a business intelligenceanalytics module 428 configured for providing business intelligencebased at least in part on the inventory transaction information.

FIG. 5 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments. Responsive to anorder from a customer, the order from the customer is deconstructed intoa financial transaction and an inventory transaction (block 500). Thefinancial transaction is translated into a unified format (block 502).An inventory transaction is translated into the unified format (block504). The transaction is posted (block 506). Business intelligenceanalytics data is generated from the transaction data (block 508).

FIG. 6 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments. Order data andpayment data are received at user-facing payment interface (block 600).A transaction ticket is generated (block 602). The transaction ticket istransmitted to a point of sale server for processing (block 604).Confirmation is received (block 606). Confirmation is displayed (block608).

FIG. 7 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments. Order data andpayment data are received to a merchant-facing mobile application (block700). A transaction ticket is generated (block 702). The transactionticket is transmitted to a point of sale server for processing (block704). Confirmation is received (block 706). Confirmation is displayed(block 708).

FIG. 8 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments. A ticket isreceived at a point of sale server (block 800). A payment processinggateway is called (block 802). Payment data is sent to the paymentgateway using the gateway application programming interface (block 804).Data is formatted for common database storage (block 806). Response isreceived from the payment gateway (block 808). Data is committed to thedatabase (block 810). Inventory is adjusted and the inventory cloud isupdated (block 812). Confirmation is sent (block 814). The transactionis posted to point of sale listeners (block 816).

FIG. 9 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments. A change order isreceived (block 900). Inventory is confirmed (block 902). The change iscommitted to the inventory database (block 904). A source is notified torelease inventory (block 906). An update is posted to inventorylisteners (block 908).

FIG. 10A illustrates a distributed system that may implement unifiedinventory and financial transaction management, according to someembodiments. An integrated electronic commerce management provider 1000manages a system 1098 for providing payment processing services from aplurality of disparate payment processors 1052-1056 to a plurality ofdisparate transaction intake platforms 10100 and 1020. Integratedelectronic commerce management provider 1000 includes, in someembodiments, a database 1002 storing electronic commerce inventory andtransaction records in a common internal format. Integrated electroniccommerce management provider 1000 includes, in some embodiments, anintegrated wireless commerce module 1004 for implementingplatform-agnostic transaction-related communication across a clientinterface 1006. An ordering customer client 10100, a merchant client1020, payment processors 1052-1056, a point of sale location 1060, aninventory resource 1070, and another point of sale location 1080communicate across network 1050 with integrated wireless commerce module1004 to implement platform-agnostic transaction-related communicationusing client interface 1006.

On ordering customer client 10100, a customer-facing order interface10102 transmits and receives transaction information (in someembodiments either or both financial and inventory) as communications10104 with client interface 1006 over network 1050. On merchant client1020, a merchant interface 1022 transmits and receives transactioninformation (in some embodiments either or both financial and inventory)as communications 1024 with client interface 1006 over network 1050.Payment processors 1052-1056 transmit and receive transactioncommunications 1064-1068 with client interface 1006 over network 1050.

In some embodiments, inventory transactions can be reported by orordered by transaction communication 1004 a-1004 n over network 1050 topoint of sale client 1062, inventory client 1072, and point of saleclient 1082. In some embodiments, inventory transactions involve thedelivery 1094 or return 1092 of delivery goods 1090. Likewise, inventorytransactions involve the transfer 1084 from a first point of salelocation 1080 to a second point of sale location 1060 or the transfer1074 from an inventory resource 1070 to a point of sale location 1060.

In some embodiments, the system 1098 includes one or more computers,such as will be discussed below with respect to FIG. 410 , configured toimplement by executing instructions on one or more processors aplatform-agnostic transaction-related communication system. In someembodiments, the transaction-related communication system includes oneor more receiving modules, which can, in some example embodiments, belocated in ordering customer client 10100, merchant client 1020, orintegrated wireless commerce module 1004, for receiving a first item offinancial transaction information from a customer-facing interface (forexample, in some embodiments order interface 10102), and receiving asecond item of financial transaction information from a merchant-facingpoint-of-sale interface (for example, in some embodiments merchantinterface 1022). As one of skill in the art will readily comprehend inlight of having read the present disclosure, any function described ashaving been performed by a module or interface of the present disclosurecan be performed by another interface or module of the presentdisclosure without departing from the scope and intent of the presentdisclosure.

In some embodiments, the transaction-related communication systemincludes a point of sale server (for example, in some embodimentslocated in ordering customer client 10100) for rendering in a commoninternal format the first item of financial transaction information fromthe customer-facing interface (for example, in some embodiments orderinterface 10102), and rendering in the common internal format the seconditem of financial transaction information from the merchant-facingpoint-of-sale interface (for example, in some embodiments merchantinterface 1022). In some embodiments, the transaction-relatedcommunication system includes a payment processing module (for example,in some embodiments, contained within integrated wireless commercemodule 1004), for rendering in a second format the first item offinancial transaction information for payment processing by a firstexternal financial party (for example, in some embodiments paymentprocessor 1052), and rendering in a third format the first item offinancial transaction information for payment processing by a secondexternal financial party (for example, in some embodiments paymentprocessor 1054).

In some embodiments, the transaction-related communication systemincludes a transaction execution module (for example, in someembodiments, contained within integrated wireless commerce module 1004),for transmitting in the second format the first item of financialtransaction information for payment processing by the first externalfinancial party (for example, in some embodiments payment processor1052), and transmitting in the third format the second item of financialtransaction information for payment processing by the second externalfinancial party (for example, in some embodiments payment processor1054).

In some embodiments, the system provides payment processing servicesfrom a plurality of disparate payment processors (for example, in someembodiments, payment processors 1054-1056) to a plurality of disparatetransaction intake platforms (for example, in some embodiments orderingcustomer client 10100 and merchant client 1020). In some embodiments,the common internal format is a common intake transaction ticket format.In some embodiments, the one or more receiving modules include a singlestack application program interface residing on one of the one or moreservers (for example, in some embodiments as a part of client interface1006). In some embodiments, the receiving the first item of financialtransaction information from the customer-facing interface (for example,in some embodiments order interface 10102) further includes receiving inthe common intake transaction ticket format over the network from amobile computing device (for example, in some embodiments orderingclient 10100) the first item of financial transaction information fromthe customer-facing interface (for example, in some embodiments orderinterface 10102). In some embodiments, the receiving the second item offinancial transaction information from the merchant-facing point-of-saleinterface (for example, in some embodiments merchant interface 1022)further includes receiving over the network in the common intaketransaction ticket format the second item of financial transactioninformation from the merchant-facing point-of-sale interface (forexample, in some embodiments merchant client 1020).

In some embodiments, the common internal format is a common intaketransaction ticket format. In some embodiments, the system furtherincludes a first translation module on a mobile computing device (forexample, in some embodiments ordering customer client 1020) forreceiving from a customer facing application including thecustomer-facing interface (for example, in some embodiments orderinterface 10102) on the mobile computing device the first item offinancial transaction information, and translating to a common intaketransaction ticket format the first item of financial transactioninformation. In some embodiments, the system further includes a secondtranslation module on a merchant-facing point of sale device (forexample, in some embodiments merchant client 1020) for receiving from amerchant facing application (for example, in some embodiments merchantinterface 1022) including the merchant-facing point-of-sale interface ona merchant point of sale device the second item of financial transactioninformation, and translating to the common intake transaction ticketformat the second item of financial transaction information.

In some embodiments, the one or more receiving modules include a singlestack application program interface residing on one of the one or moreservers (for example, in some embodiments in client interface 10102). Insome embodiments, the server (for example, in some embodimentsintegrated wireless commerce module 1004) communicates (for example, insome embodiments sending and receiving communications 10104) remotelywith the mobile computing device (for example, in some embodimentscustomer ordering client 10100) over a wireless network (for example, insome embodiments network 1050). In some embodiments, the server (forexample, in some embodiments integrated wireless commerce module 1004)communicates remotely with the merchant-facing point of sale device overa second network. In some embodiments, the receiving the first item offinancial transaction information from the customer-facing interface(for example, in some embodiments in order interface 10102) furtherincludes receiving in the common intake transaction ticket format at thesingle stack application interface (for example, in some embodiments inclient interface 1006) from the mobile computing device the first itemof financial transaction information from the customer-facing interface(for example, in some embodiments in ordering interface 10102). In someembodiments, the receiving the second item of financial transactioninformation from the merchant-facing point-of-sale interface furtherincludes receiving in the common intake transaction ticket format at thesingle stack application interface (for example, in some embodiments inclient interface 1006) the second item of financial transactioninformation from the merchant-facing point-of-sale interface (forexample, in some embodiments merchant interface 1022).

In some embodiments, the transaction execution module (for example, insome embodiments in integrated wireless commerce module 1004) is furtherconfigured for receiving on the one or more servers a transactionauthorization confirmation from the first external financial party, andthe point of sale server (for example, in some embodiments in integratedwireless commerce module 1004) is further configured for transmitting tothe customer-facing interface (for example, in some embodiments orderinterface 10102) an indication of the transaction authorizationconfirmation. In some embodiments, the payment processing moduleincludes a payment processing gateway (for example, in some embodimentsin client interface 1006) for communicating with servers of externalfinancial processors (for example, in some embodiments paymentprocessors 1052-1056) using encrypted links over a network 1050.

In some embodiments, the system for providing payment processingservices from a plurality of disparate payment processors (for example,in some embodiments payment processors 1052-1056) to a plurality ofdisparate transaction intake platforms further includes a businessintelligence analytics module (for example, in some embodiments inintegrated wireless commerce module 1004) for providing businessintelligence based at least in part on the first item of financialtransaction information.

In some embodiments, the system for providing payment processingservices from a plurality of disparate payment processors (for example,in some embodiments payment processors 1052-1056) to a plurality ofdisparate transaction intake platforms (for example, in some embodimentsmerchant client 1020 and ordering customer client 10100) furtherincludes an inventory coordination module (for example, in someembodiments in integrated wireless commerce module 1004) for providingtransaction fulfillment information based at least in part on the firstitem of financial transaction information.

In some embodiments, the inventory coordination module enables theintegrated wireless commerce module 1004 to monitor consolidated stocklevels and determine when to re-order, without relying on additionalsystems or manual reporting, thereby enabling merchants to provide aconsistent, seamless experience for consumers across all channels,including offering returns through any channel no matter where thepurchase originated. Some embodiments of integrated wireless commercemodule 1004 support a merchant that operates a physical store, operatesan online store, accepts payments on a mobile device, or any combinationof those channels. Some embodiments of integrated wireless commercemodule 1004 present a single merchant account to reduce reconciliationand accounting headaches and to provide one version of the data throughconsolidated reports across all channels and touchpoints. Someembodiments of integrated wireless commerce module 1004 can also handlethe issues of managing inventory across mobile and e-commercetouchpoints, as well as in the store, providing a single view of themerchandise that's available to sell, and helping businesses balancebetween inventory and demand.

Some embodiments of integrated wireless commerce module 1004 support acloud-based point-of-sale, mobile and eCommerce framework thatintegrates payments with inventory management.

Some embodiments of integrated wireless commerce module 1004 real-time,in-app inventory tracking, management and replenishment directly from amobile application. Some embodiments of integrated wireless commercemodule 1004 provide import and export capabilities that allow merchantsto easily transfer and integrate inventory data into other systems. Someembodiments of integrated wireless commerce module 1004 provideIntegration with third party eCommerce platforms—sales and inventorydata by location provides merchants more valuable insights into theirbusiness. Some embodiments of integrated wireless commerce module 1004provide the ability to set replenishment thresholds and alerts andtransfer inventory between locations and channels. Some embodiments ofintegrated wireless commerce module 1004 adjust inventory for sales andreturns in real-time and can also work with a merchant's existinginventory platform, by allowing merchants to integrate in to someembodiments of integrated wireless commerce module 1004 usingapplication program interfaces.

Some embodiments of integrated wireless commerce module 1004 can alsosolve the problems of the friction points mentioned above by eliminatingdisparate payment processors and processing rates, further simplifyingreconciliation across all of a merchant's selling channels. In moving toa single payments provider under some embodiments, merchants can alsotake advantage of volume pricing, and get the best possible rates foreach channel.

Some embodiments of integrated wireless commerce module 1004 providebusiness insights, such merchants can leverage data to optimize sales,for example such as how much floor space to allocate to specificproducts, what items and locations provide the most revenue and profitand what products to feature. Merchants also have the ability to storecustomer history, past purchases and other customer-specific data tohelp them become more customer-centric. These systems open the door tointegrated loyalty programs and other customer relationship managementtools to help merchants know who their best customers are and how tobest reach them how, when and where the customer wants to shop.

Some embodiments of integrated wireless commerce module 1004 also allowdevelopers to integrate payments, inventory and business insights intotheir platforms through the only single stack of application programinterfaces for card present and card not present transactions.

Some embodiments of integrated wireless commerce module 1004 alsoinclude a system for providing inventory management services from aplurality of disparate inventory resources (for example, in someembodiments point of sale location 1060, inventory resource 1070 andpoint of sale location 1080) for transactions received from a pluralityof disparate transaction intake platforms (for example, in someembodiments ordering customer client 10100 and merchant client 1020). Insome embodiments, one or more computers executes instructions on one ormore processors for a platform-agnostic transaction-relatedcommunication system. In some embodiments, the transaction-relatedcommunication system includes one or more receiving modules, which can,in some example embodiments, be located in ordering customer client10100, merchant client 1020, or integrated wireless commerce module1004, point of sale client 1062, inventory client 1072, or point of salelocation 1082, configured for receiving a first item of inventorytransaction information from a customer-facing interface, and receivinga second item of inventory transaction information from amerchant-facing point-of-sale interface.

In some embodiments, the transaction-related communication systemincludes an inventory coordination module (for example, in someembodiments, contained within integrated wireless commerce module 1004),configured for rendering in a common internal format the first item ofinventory transaction information from the customer-facing interface(for example, in some embodiments order interface 10102), and renderingin the common internal format the second item of inventory transactioninformation from the merchant-facing point-of-sale interface (forexample, in some embodiments, merchant interface 1022). In someembodiments, the transaction-related communication system includes aninventory coordination module configured for transmitting the seconditem of inventory transaction information for inventory transactionexecution by the second inventory resource (for example, in someembodiments, a warehouse such as inventory resource 1070), andtransmitting the first item of inventory transaction information forinventory transaction execution by a first inventory resource (forexample, in some embodiments, point of sale location 1060).

In some embodiments, the transaction-related communication systemincludes a synchronization server module (for example, in someembodiments, contained within integrated wireless commerce module 1004)configured for providing background updates of transactions to thecustomer facing interface and the merchant-facing point of saleinterface (for example, in some embodiments ordering customer client10100 and merchant client 1020). In some embodiments, the receiving thefirst item of inventory transaction information from the customer-facinginterface further includes receiving in the common intake transactionticket format over the network from a mobile computing device an orderfor an item as the first item of inventory transaction information fromthe customer-facing interface (for example, in some embodiments orderingcustomer client 10100). In some embodiments, the receiving the seconditem of inventory transaction information from the merchant-facingpoint-of-sale interface further includes receiving over the network inthe common intake transaction ticket format a return of the item as thesecond item of inventory transaction information from themerchant-facing point-of-sale interface (for example, in someembodiments merchant client 1020). In some embodiments, the inventorycoordination module is further configured for updating a unifiedinventory database (for example, in some embodiments database 1002) toreflect fulfillment of the order for the item, and the inventorycoordination module is further configured for updating a unifiedinventory database (for example, in some embodiments database 1002) toreflect fulfillment of the return of the item.

In some embodiments, the receiving the first item of inventorytransaction information from the customer-facing interface (for example,in some embodiments ordering customer client 10100) further includesreceiving in the common intake transaction ticket format over thenetwork from a mobile computing device an order for an item as the firstitem of inventory transaction information from the customer-facinginterface (for example, in some embodiments order interface 10102). Insome embodiments, the receiving the second item of inventory transactioninformation from the merchant-facing point-of-sale interface (forexample, in some embodiments merchant client 1020) further includesreceiving over the network in the common intake transaction ticketformat a return of the item as the second item of inventory transactioninformation from the merchant-facing point-of-sale interface (forexample, in some embodiments merchant interface 1022). In someembodiments, the inventory coordination module is further configured forquerying a unified inventory database (for example, in some embodimentsdatabase 1002) to ascertain whether fulfillment of the order for theitem is possible, and the inventory coordination module is furtherconfigured for updating a unified inventory database (for example, insome embodiments database 1002) to reflect fulfillment of the return ofthe item.

In some embodiments, the common internal format is a common intaketransaction ticket format, and the one or more receiving modules includea single stack application program interface residing on one of the oneor more servers.

In some embodiments, the receiving the first item of inventorytransaction information from the customer-facing interface furtherincludes receiving in the common intake transaction ticket format overthe network from a mobile computing device (for example, in someembodiments ordering customer client 10100) an order for an item as thefirst item of inventory transaction information from the customer-facinginterface (for example, in some embodiments order interface 10102). Insome embodiments, the receiving the second item of inventory transactioninformation from the merchant-facing point-of-sale interface (forexample, in some embodiments merchant client 1020) further includesreceiving over the network in the common intake transaction ticketformat a return of the item as the second item of inventory transactioninformation from the merchant-facing point-of-sale interface (forexample, in some embodiments merchant interface 1022). In someembodiments, the inventory coordination module is further configured forupdating a unified inventory database (for example, in some embodimentsdatabase 1002) to reflect fulfillment of the order for the item from aninventory warehouse resource. In some embodiments, the inventorycoordination module is further configured for updating a unifiedinventory database (for example, in some embodiments database 1002) toreflect fulfillment of the return of the item by updating an in-stockinventory count for a brick-and-mortar retail location (for example, insome embodiments point of sale location 1080) housing themerchant-facing point-of-sale interface (for example, in someembodiments point of sale client 1082).

In some embodiments, the system further includes a business intelligenceanalytics module (for example, in some embodiments, contained withinintegrated wireless commerce module 104) configured for providingbusiness intelligence based at least in part on the inventorytransaction information. FIG. 10B is a flowchart of a process forunified inventory and financial transaction management, according tosome embodiments. Routing is ascertained (block 1000). A merchant isauthenticated (block 1002). Formatting of the transaction for a provider(payment front end) is performed (block 1004). The transaction is sentto a provider (block 1006). An authorization or decline is received(block 1008). The authorization or decline response is transmitted tothe point-of-sale server (block 1010).

FIG. 11 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments. A first item offinancial transaction information is received from a customer-facinginterface (block 1100). A second item of financial transactioninformation is received from a merchant-facing point-of-sale interface(block 1102). The first item of financial transaction information fromthe customer-facing interface is rendered in a common internal format(block 1104). The second item of financial transaction information fromthe merchant-facing point-of-sale interface is rendered in the commoninternal format (block 1106). A first item of financial transactioninformation for payment processing by a second external financial partyis rendered in a third format (block 1108). The first item of financialtransaction information is transmitted in the third format for paymentprocessing by the first external financial party (block 1110). Thesecond item of financial transaction information is transmitted in thethird format for payment processing by the second external financialparty (block 1112).

FIG. 12 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments. A first item offinancial transaction information is received from a customer facingapplication including a customer-facing interface on the mobilecomputing device (block 1200). A second item of financial transactioninformation is received from a merchant facing application including themerchant-facing point-of-sale interface on a merchant point of saledevice (block 1202). The first item of financial transaction informationis translated to a common intake transaction ticket format (block 1204).The second item of financial transaction information is translated tothe common intake transaction ticket format (block 1206).

FIG. 13 is a flowchart of a process for unified inventory and financialtransaction management, according to some embodiments. A transactionauthorization confirmation from the first external financial party isreceived on one or more servers (block 1300). An indication of thetransaction authorization confirmation is transmitted to thecustomer-facing interface (block 1302).

FIG. 14 is a user interface for creating a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 15 is a user interface for creating a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 16 is a user interface for creating a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 17 is a user interface for creating a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 18 is a user interface for creating a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 19 is a user interface for selecting for review a sales ticket forunified inventory and financial transaction management, according tosome embodiments.

FIG. 20 is a user interface for reviewing a sales ticket for unifiedinventory and financial transaction management, according to someembodiments.

FIG. 21 is a user interface for selecting for review an item in a salesticket for unified inventory and financial transaction management,according to some embodiments.

FIG. 22 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 23 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 24 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 25 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 26 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 27 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 28 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 29 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 30 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 31 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 32 is a user interface for reviewing an overview of inventory in asystem for unified inventory and financial transaction management,according to some embodiments.

FIG. 33 is a user interface for reviewing an overview of transactions ina system for unified inventory and financial transaction management,according to some embodiments.

FIG. 34 is a user interface for recording a transaction in a system forunified inventory and financial transaction management, according tosome embodiments.

FIG. 35 is a user interface for reporting a transaction in a system forunified inventory and financial transaction management, according tosome embodiments.

FIG. 36 is a flowchart of a synchronization method for unified inventoryand financial transaction management, according to some embodiments. Apointer for a serial number indicating a last updated object received isreceived from the client (block 3600). A list of objects or object typesfor update is received (block 3602). Subsequent objects are transmitted(block 3604).

FIG. 37 is a flowchart of a method for unified inventory transactionmanagement, according to some embodiments. A first item of inventorytransaction information is received from a customer-facing interface(block 3700). A second item of inventory transaction information isreceived from a merchant-facing point-of-sale interface (block 3702).The first item of inventory transaction information from thecustomer-facing interface is rendered in a common internal format (block3704). The second item of inventory transaction information from thecustomer-facing interface is rendered in the common internal format(block 3706). The first item of inventory transaction information istransmitted for inventory transaction execution by a first inventoryresource (block 3708). The second item of inventory transactioninformation is transmitted for inventory transaction execution by thesecond inventory resource (block 3710).

FIG. 38 is a flowchart of a method for unified inventory transactionmanagement, according to some embodiments. A first item of inventorytransaction information is received from a customer-facing interface(block 3800). A second item of inventory transaction information isreceived from a merchant-facing point-of-sale interface (block 3802).The first item of inventory transaction information from thecustomer-facing interface is rendered in a common internal format (block3804). The second item of inventory transaction information from thecustomer-facing interface is rendered in the common internal format(block 3806). The first item of inventory transaction information istransmitted for inventory transaction execution by a first inventoryresource (block 3808). The second item of inventory transactioninformation is transmitted for inventory transaction execution by thesecond inventory resource (block 3810). Background updates oftransactions are provided to the customer facing interface and themerchant-facing point of sale interface (block 3812).

FIG. 39 is a flowchart of a method for unified inventory transactionmanagement, according to some embodiments. A first item of inventorytransaction information is received from a customer-facing interface byreceiving in the common intake transaction ticket format over thenetwork from a mobile computing device an order for an item as the firstitem of inventory transaction information from the customer-facinginterface (block 3900). A second item of inventory transactioninformation is received from a merchant-facing point-of-sale interfaceby receiving over the network in the common intake transaction ticketformat a return of the item as the second item of inventory transactioninformation from the merchant-facing point-of-sale interface (block3902). The first item of inventory transaction information from thecustomer-facing interface is rendered in a common internal format (block3904). The second item of inventory transaction information from thecustomer-facing interface is rendered in the common internal format(block 3906). The first item of inventory transaction information istransmitted for inventory transaction execution by a first inventoryresource (block 3908). The second item of inventory transactioninformation is transmitted for inventory transaction execution by thesecond inventory resource (block 3910). A unified inventory database isupdated to reflect fulfillment of the order for the item and update(block 3912). The unified inventory database is updated to reflectfulfillment of the return of the item (block 3914.)

FIG. 40 is a flowchart of a method for unified inventory transactionmanagement, according to some embodiments. A first item of inventorytransaction information is received from a customer-facing interface byreceiving in the common intake transaction ticket format over thenetwork from a mobile computing device an order for an item as the firstitem of inventory transaction information from the customer-facinginterface (block 3900). A second item of inventory transactioninformation is received from a merchant-facing point-of-sale interfaceby receiving over the network in the common intake transaction ticketformat a return of the item as the second item of inventory transactioninformation from the merchant-facing point-of-sale interface (block3902). The first item of inventory transaction information from thecustomer-facing interface is rendered in a common internal format (block3904). The second item of inventory transaction information from thecustomer-facing interface is rendered in the common internal format(block 3906). The first item of inventory transaction information istransmitted for inventory transaction execution by a first inventoryresource (block 3908). The second item of inventory transactioninformation is transmitted for inventory transaction execution by thesecond inventory resource (block 3910). A unified inventory database isqueried to ascertain whether the order for the item is possible (block3912). The unified inventory database is updated to reflect fulfillmentof the return of the item (block 3914.)

Example System

Embodiments of an electronic commerce management module and/or of theproduction resources management techniques as described herein may beexecuted on one or more computer systems, which may interact withvarious other devices. One such computer system is illustrated by FIG.41 . In different embodiments, computer system 4100 may be any ofvarious types of devices, including, but not limited to, a personalcomputer system, desktop computer, laptop, notebook, or netbookcomputer, mainframe computer system, handheld computer, workstation,network computer, a camera, a set top box, a mobile device, a consumerdevice, video game console, handheld video game device, applicationserver, storage device, a peripheral device such as a switch, modem,router, or in general any type of computing or electronic device.

In the illustrated embodiment, computer system 4100 includes one or moreprocessors 4110 coupled to a system memory 4120 via an input/output(I/O) interface 4130. Computer system 4100 further includes a networkinterface 4140 coupled to I/O interface 4130, and one or moreinput/output devices 4150, such as cursor control device 4160, keyboard4170, and display(s) 4180. In some embodiments, it is contemplated thatembodiments may be implemented using a single instance of computersystem 4100, while in other embodiments multiple such systems, ormultiple nodes making up computer system 4100, may be configured to hostdifferent portions or instances of embodiments. For example, in oneembodiment some elements may be implemented via one or more nodes ofcomputer system 4100 that are distinct from those nodes implementingother elements.

In various embodiments, computer system 4100 may be a uniprocessorsystem including one processor 4110, or a multiprocessor systemincluding several processors 4110 (e.g., two, four, eight, or anothersuitable number). Processors 4110 may be any suitable processor capableof executing instructions. For example, in various embodiments,processors 4110 may be general-purpose or embedded processorsimplementing any of a variety of instruction set architectures (ISAs),such as the x86, PowerPC, SPARC, or MIPS ISAs, or any other suitableISA. In multiprocessor systems, each of processors 4110 may commonly,but not necessarily, implement the same ISA.

In some embodiments, at least one processor 4110 may be a graphicsprocessing unit. A graphics processing unit or GPU may be considered adedicated graphics-rendering device for a personal computer,workstation, game console or other computing or electronic device.Modern GPUs may be very efficient at manipulating and displayingcomputer graphics, and their highly parallel structure may make themmore effective than typical CPUs for a range of complex graphicalalgorithms. For example, a graphics processor may implement a number ofgraphics primitive operations in a way that makes executing them muchfaster than drawing directly to the screen with a host centralprocessing unit (CPU). In various embodiments, the image processingmethods disclosed herein may, at least in part, be implemented byprogram instructions configured for execution on one of, or parallelexecution on two or more of, such GPUs. The GPU(s) may implement one ormore application programmer interfaces (APIs) that permit programmers toinvoke the functionality of the GPU(s). Suitable GPUs may becommercially available from vendors such as NVIDIA Corporation, ATITechnologies (AMD), and others.

System memory 4120 may be configured to store program instructionsand/or data accessible by processor 4110. In various embodiments, systemmemory 4120 may be implemented using any suitable memory technology,such as static random access memory (SRAM), synchronous dynamic RAM(SDRAM), nonvolatile/Flash-type memory, or any other type of memory. Inthe illustrated embodiment, program instructions and data implementingdesired functions, such as those described above for embodiments of anelectronic commerce management module are shown stored within systemmemory 4120 as program instructions 4125 and data storage 4135,respectively. In other embodiments, program instructions and/or data maybe received, sent or stored upon different types of computer-accessiblemedia or on similar media separate from system memory 4120 or computersystem 4100. Generally speaking, a computer-accessible medium mayinclude storage media or memory media such as magnetic or optical media,e.g., disk or CD/DVD-ROM coupled to computer system 4100 via I/Ointerface 4130. Program instructions and data stored via acomputer-accessible medium may be transmitted by transmission media orsignals such as electrical, electromagnetic, or digital signals, whichmay be conveyed via a communication medium such as a network and/or awireless link, such as may be implemented via network interface 4140.

In one embodiment, I/O interface 4130 may be configured to coordinateI/O traffic between processor 4110, system memory 4120, and anyperipheral devices in the device, including network interface 4140 orother peripheral interfaces, such as input/output devices 4150. In someembodiments, I/O interface 4130 may perform any necessary protocol,timing or other data transformations to convert data signals from onecomponent (e.g., system memory 4120) into a format suitable for use byanother component (e.g., processor 4110). In some embodiments, I/Ointerface 4130 may include support for devices attached through varioustypes of peripheral buses, such as a variant of the Peripheral ComponentInterconnect (PCI) bus standard or the Universal Serial Bus (USB)standard, for example. In some embodiments, the function of I/Ointerface 4130 may be split into two or more separate components, suchas a north bridge and a south bridge, for example. In addition, in someembodiments some or all of the functionality of I/O interface 4130, suchas an interface to system memory 4120, may be incorporated directly intoprocessor 4110.

Network interface 4140 may be configured to allow data to be exchangedbetween computer system 4100 and other devices attached to a network,such as other computer systems, or between nodes of computer system4100. In various embodiments, network interface 4140 may supportcommunication via wired or wireless general data networks, such as anysuitable type of Ethernet network, for example; viatelecommunications/telephony networks such as analog voice networks ordigital fiber communications networks; via storage area networks such asFibre Channel SANs, or via any other suitable type of network and/orprotocol.

Input/output devices 4150 may, in some embodiments, include one or moredisplay terminals, keyboards, keypads, touchpads, scanning devices,voice or optical recognition devices, or any other devices suitable forentering or retrieving data by one or more computer system 4100.Multiple input/output devices 4150 may be present in computer system4100 or may be distributed on various nodes of computer system 4100. Insome embodiments, similar input/output devices may be separate fromcomputer system 4100 and may interact with one or more nodes of computersystem 4100 through a wired or wireless connection, such as over networkinterface 4140.

As shown in FIG. 41 , memory 4120 may include program instructions 4125,configured to implement embodiments of an electronic commerce managementmodule as described herein, and data storage 4135, including variousdata accessible by program instructions 4125. In one embodiment, programinstructions 4125 may include software elements of embodiments of anelectronic commerce management module as illustrated in the aboveFigures. Data storage 4135 may include data that may be used inembodiments. In other embodiments, other or different software elementsand data may be included.

Those skilled in the art will appreciate that computer system 4100 ismerely illustrative and is not intended to limit the scope of anelectronic commerce management module as described herein. Inparticular, the computer system and devices may include any combinationof hardware or software that can perform the indicated functions,including a computer, personal computer system, desktop computer,laptop, notebook, or netbook computer, mainframe computer system,handheld computer, workstation, network computer, a camera, a set topbox, a mobile device, network device, internet appliance, PDA, wirelessphones, pagers, a consumer device, video game console, handheld videogame device, application server, storage device, a peripheral devicesuch as a switch, modem, router, or in general any type of computing orelectronic device. Computer system 4100 may also be connected to otherdevices that are not illustrated, or instead may operate as astand-alone system. In addition, the functionality provided by theillustrated components may in some embodiments be combined in fewercomponents or distributed in additional components. Similarly, in someembodiments, the functionality of some of the illustrated components maynot be provided and/or other additional functionality may be available.

Those skilled in the art will also appreciate that, while various itemsare illustrated as being stored in memory or on storage while beingused, these items or portions of them may be transferred between memoryand other storage devices for purposes of memory management and dataintegrity. Alternatively, in other embodiments some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated computer system via inter-computercommunication. Some or all of the system components or data structuresmay also be stored (e.g., as instructions or structured data) on acomputer-accessible medium or a portable article to be read by anappropriate drive, various examples of which are described above. Insome embodiments, instructions stored on a computer-accessible mediumseparate from computer system 4100 may be transmitted to computer system4100 via transmission media or signals such as electrical,electromagnetic, or digital signals, conveyed via a communication mediumsuch as a network and/or a wireless link. Various embodiments mayfurther include receiving, sending or storing instructions and/or dataimplemented in accordance with the foregoing description upon acomputer-accessible medium. Accordingly, the present invention may bepracticed with other computer system configurations.

CONCLUSION

Various embodiments may further include receiving, sending or storinginstructions and/or data implemented in accordance with the foregoingdescription upon a computer-accessible medium. Generally speaking, acomputer-accessible medium may include storage media or memory mediasuch as magnetic or optical media, e.g., disk or DVD/CD-ROM, volatile ornon-volatile media such as RAM (e.g. SDRAM, DDR, RDRAM, SRAM, etc.),ROM, etc., as well as transmission media or signals such as electrical,electromagnetic, or digital signals, conveyed via a communication mediumsuch as network and/or a wireless link.

The various methods as illustrated in the Figures and described hereinrepresent example embodiments of methods. The methods may be implementedin software, hardware, or a combination thereof. The order of method maybe changed, and various elements may be added, reordered, combined,omitted, modified, etc.

Various modifications and changes may be made as would be obvious to aperson skilled in the art having the benefit of this disclosure. It isintended that the invention embrace all such modifications and changesand, accordingly, the above description to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A device comprising: a memory configured to storeinstructions; and a processor configured to execute the instructions toperform operations comprising: receiving a first item of inventorytransaction information from a customer-facing interface; receiving asecond item of inventory transaction information from a merchant-facingpoint-of-sale interface; rendering the first item of inventorytransaction information in a common internal format; rendering thesecond item of inventory transaction information in the common internalformat; transmitting the first item of inventory transaction informationfor inventory transaction execution by a first inventory resource; andtransmitting the second item of inventory transaction information forinventory transaction execution by a second inventory resource.
 2. Thedevice according to claim 1, wherein the operations further comprise:providing a background update of a transaction to the customer-facinginterface and the merchant-facing interface.
 3. The device according toclaim 1, wherein: the receiving the first item of inventory transactioninformation comprises receiving an order for an item in a common intaketransaction ticket format over a network from a mobile computing device;and the receiving the second item of inventory transaction informationcomprises receiving a return of the item in the common intaketransaction ticket format over the network from the merchant-facingpoint-of-sale interface.
 4. The device according to claim 3, wherein theoperations further comprise: updating a unified inventory database toreflect fulfillment of the order for the item.
 5. The device accordingto claim 3, wherein the operations further comprise: updating a unifiedinventory database to reflect fulfillment of the return of the item. 6.The device according to claim 3, wherein the operations furthercomprise: querying a unified inventory database to ascertain whetherfulfillment of the order is possible.
 7. The device according to claim6, wherein the operations further comprise: updating the unifiedinventory database to reflect the fulfillment of the return of the item.8. A method comprising: receiving a first item of inventory transactioninformation from a customer-facing interface; receiving a second item ofinventory transaction information from a merchant-facing point-of-saleinterface; rendering the first item of inventory transaction informationin a common internal format; rendering the second item of inventorytransaction information in the common internal format; transmitting thefirst item of inventory transaction information for inventorytransaction execution by a first inventory resource; and transmittingthe second item of inventory transaction information for inventorytransaction execution by a second inventory resource.
 9. The methodaccording to claim 8, further comprising: providing a background updateof a transaction to the customer-facing interface and themerchant-facing interface.
 10. The method according to claim 8, wherein:the receiving the first item of inventory transaction informationcomprises receiving an order for an item in a common intake transactionticket format over a network from a mobile computing device; and thereceiving the second item of inventory transaction information comprisesreceiving a return of the item in the common intake transaction ticketformat over the network from the merchant-facing point-of-saleinterface.
 11. The method according to claim 10, further comprising:updating a unified inventory database to reflect fulfillment of theorder for the item.
 12. The method according to claim 10, furthercomprising: updating a unified inventory database to reflect fulfillmentof the return of the item.
 13. The method according to claim 10, furthercomprising: querying a unified inventory database to ascertain whetherfulfillment of the order is possible.
 14. The method according to claim13, further comprising: updating the unified inventory database toreflect fulfillment of the return of the item.
 15. A non-transitorycomputer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by one or moreprocessors of a device, cause the one or more processors to performoperations comprising: receiving a first item of inventory transactioninformation from a customer-facing interface; receiving a second item ofinventory transaction information from a merchant-facing point-of-saleinterface; rendering the first item of inventory transaction informationin a common internal format; rendering the second item of inventorytransaction information in the common internal format; transmitting thefirst item of inventory transaction information for inventorytransaction execution by a first inventory resource; and transmittingthe second item of inventory transaction information for inventorytransaction execution by a second inventory resource.
 16. Thenon-transitory computer-readable medium according to claim 15, whereinthe operations further comprise: providing a background update of atransaction to the customer-facing interface and the merchant-facinginterface.
 17. The non-transitory computer-readable medium according toclaim 15, wherein: the receiving the first item of inventory transactioninformation comprises receiving an order for an item in a common intaketransaction ticket format over a network from a mobile computing device;and the receiving the second item of inventory transaction informationcomprises receiving a return of the item in the common intaketransaction ticket format over the network from the merchant-facingpoint-of-sale interface.
 18. The non-transitory computer-readable mediumaccording to claim 17, wherein the operations further comprise: updatinga unified inventory database to reflect fulfillment of the order for theitem.
 19. The non-transitory computer-readable medium according to claim17, wherein the operations further comprise: updating a unifiedinventory database to reflect fulfillment of the return of the item. 20.The non-transitory computer-readable medium according to claim 17,wherein the operations further comprise: querying a unified inventorydatabase to ascertain whether fulfillment of the order is possible.